Jeremy O - Medidata - Hi -- I created a support...
Hi -- I created a support ticket here and was directed here to Discord. I am having an issue where the Import Metadata API is returning incorrect 'request_index', which causes a pretty large issue in our usage because we are using this for promoting metadata objects between orgs. We need to be able to map the individual metadata responses to the requests in order to do our own uuid mappings during metadata creation in the same way ThoughtSpot does it in the github integration.
If this is a bug, can someone help me figure out either a workaround or let me know if it can be fixed? If I can rely on the order of the response array matching the request array that is one workaround I can think of but I couldn't get confirmation of this in the docs.
2 Replies
Can you post the error you are getting?
We had faced a similar issue and told by TS team that request_index is for internal purpose. We changed our logic to use 'name' of the objects to verify which resource is imported and which failed. Not sure why 'internal purpose' fields are exposed as API response but that's what we got.