API M - 1 Relationship issue

[ssommerfeldt]

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]

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]

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

[FelixMalfait]

Hey @ssommerfeldt let's do another call maybe? Feel free to book anytime: cal.com/ifelix/25min
It depends on your timeline, we'll have something that will make it 10x easier for you, but not short-term

A few notes:

• For primary lead source you're sure you want to create a relationship and not a Select field type?
• @magrinj is working on updating the relationship api to simplify it
• We use graphql internally. If it's an option for you I would recommend using it, that way you can do your query in the UI and then copy/paste from your browser's inspector to your codebase