Comments
-
@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?
