You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope I am just doing something incorrectly but ultimately want to know how do I correctly create a M -1 Relationship through the API.
What I am doing is creating a Bundler application where you can bundle up custom schema created in one environment and move it to another environment like bundleing up changes made in Sandbox and moving them to TEST or PROD
Thanks,
Scott
The text was updated successfully, but these errors were encountered:
Hey Scott, we'll have a look at the underlying problem but I'm hoping we could help you build something more efficient than just accessing the raw metadata api. We already have similar problems internally and have already built a lot of tooling to sync standard objects to multiple workspaces that start from a different state ('sync-metadata' command). This problem isn't that different. I need to think about this but we should build something to make your life easier here.
Greetings Team
I suspect there is an issue When using GET http://localhost:3000/rest/metadata/objects
M -1 Relationships are returned incorrectly.
See video
https://www.loom.com/share/ee8d1c00ec7440f9b6a5513d7491f8e5?sid=67a31cdf-0106-4b39-8058-44aa5dfbc96d
Here is the sample Json
_test M-1 Relationship.json
I hope I am just doing something incorrectly but ultimately want to know how do I correctly create a M -1 Relationship through the API.
What I am doing is creating a Bundler application where you can bundle up custom schema created in one environment and move it to another environment like bundleing up changes made in Sandbox and moving them to TEST or PROD
Thanks,
Scott
The text was updated successfully, but these errors were encountered: