sourabh05

@Mehdi This sugarforce tutorial has a section at the bottom to add proxy:

in Custom Domo App (Replicating the SugarForce example) Comment by sourabh05 November 13

Closing the loop on this one. I realize that the new method of initiating an app instance does not install domo.js on the project. But it links the library through CDN and the info can be found in the script tag. I ended up manually copying the domo.js file from another project to resolve that error. But at some later…

in Domo.JS is not getting created via domo init Comment by sourabh05 November 11

Thanks for your feedback @ArborRose. My issue is that domo init is not generating/deploying domo.js. I even tried to install it manually and it says 'up to date, audited 2 packages in 940ms. But when I check the folder, there's nothing.

in Domo.JS is not getting created via domo init Comment by sourabh05 October 24

@MattTheGuru your suggestion worked! It needed a proxy and as soon as I added that I am able to successfully retrieve the object through get method. So apparently proxy is needed for both AppDB and Data APIs. And I am able to do this in the local dev server. Thank you!!

in Custom Domo App (Replicating the SugarForce example) Comment by sourabh05 October 2

yes, I want to run it locally (in the dev instance using domo dev CLI command) before I release the app to the Domo instance. I was thinking about setting up a proxy but all the documentation says that proxy is only needed for the AppDB not for the Data APIs.

in Custom Domo App (Replicating the SugarForce example) Comment by sourabh05 September 30

Hi @MattTheGuru - Thanks for your feedback. Those attributes were created by the SugarForce template but in any case, I tried changing those to what you mentioned above and that still does not work.

in Custom Domo App (Replicating the SugarForce example) Comment by sourabh05 September 30

Added token authorization, still no bueno