sourabh05 Member

Thanks for the response @GrantSmith ! Syn was enabled but I wanted to trigger this manually right after an update is made to the appDB. This was helpful!

Here's what the document look like:

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

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…

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.

@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!!

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.

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.

Added token authorization, still no bueno

Added Embed authorization to the localhost (although, I don't think this should matter), to no avail

also, I got the same get request error for the second tutorial 'Return Flow'

I tried running on my local dev instance to eliminate the permissions issue with the company instance.. but the same error with the local dev instance

I tried installing domo,js as per instructions here: And I see that the ryuu.js package was installed but no domo.js still (updated): I see that Domo.js is now part of the installed package.

same error with the v1

Thanks for the suggestion, @GrantSmith. I do have the alias 'leads' setup in the manifest as per the instructions. "datasetsMapping":[ { "dataSetId": <ID>, "alias": "leads", "fields": [] } ], Although, when I was comparing the code published on that tutorial I can see that Domo.js was missing in my setup. I am assuming…

I wonder if there was an update on this issue?