API Problem after addind a new entity to the app (Bug)
Hi i was using a shopify api and it was working fine with all my virtual entities and after creating a new one and conecting the new to the response entity used by the api the app stop working and even if i remove the conection between the two entities i still have the same error , like if the app is broken . Is there a solution for this ?
-
Official comment
I tried to duplicate the consumable in the same app but got strange errors on each attempt trying to test the API call. So I built the same consumable and entities in the Sandbox app that we have. And it was pretty straight forward. I did not add all the properties into all of the entities, but I made sure to try out the collections so that we know it works.
Do you have access to our Sandbox application? I think we might need to ping the product team about your application and see whats going on, and why we get the errors.
Conclusion: I looks like you had made everything right according to best practice. You were a bit unlucky with the environment.
-
The new entity that you added, was a collection or just a sub-entity added to the response? Did you also restart the session from studio before testing?
0 -
was a connected entity list that i added to my response , actually i dind't restart the session i will try it
0 -
restart the session doesn't work
0 -
Ok, this usually does causes any problems. Is it possible to invite me to the application and I can have a second look?
Do you also have an example on how the response should look like? Like in JSON format?0 -
Great, I am in the community now!
0 -
added to the project
0 -
I cant press the "Open" button. Also added the same command to the sidebar, but cant run it even there. A bit strange?
0 -
Could you also invite stellan.andersson@flowfactory.com to the community and the app as well?
0 -
Hi , yes i will invite him right away
0 -
invite sent
0 -
do you need manager roles for the project?
0 -
The problem is now solved in your application according to the platform team. There was a problem with property mappings. We have created an issue for upcoming sprint to try to prevent this happening again.
0
Please sign in to leave a comment.
Comments
13 comments