Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API M - 1 Relationship issue #9625

Open
ssommerfeldt opened this issue Jan 14, 2025 · 2 comments
Open

API M - 1 Relationship issue #9625

ssommerfeldt opened this issue Jan 14, 2025 · 2 comments

Comments

@ssommerfeldt
Copy link

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

@FelixMalfait
Copy link
Member

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.

@ssommerfeldt
Copy link
Author

Felix

Thanks for looking at this. If you have tools to make this a little easier to move metadata that would be awesome.

Cheers,

Scott

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants