Add a record with odata.id null

(1) Share

Report

Posted on by fsuarezoedt

I want to add a record in a table but there are cases where I have a contact in that record and cases where I do NOT have a contact. So right now I'm using a conditional asking if the contact is null, and two actions to Add the record.

For other kinds of data, like strings, I can simply put the value in the field of a single Add record action and that will do. If the value is null, nothing will happen.

But for odata.id I get an error telling me that it can't be null.

My question is: Is there a way to use a single Add record with a formula that I'm missing?

Thanks!

Categories:

Business Process Flows

All responses (2)

Answers (0)

fsuarezoedt 46 on at

Like (0)

Report

Add a record with odata.id null

Hi FLMike

Yes, my Opportunities table has a relationship with the Contact table.

But in some cases, I don't need to add that field in a record, and in some cases, I DO need to add it.

Then, If I create a single Add record and put a variable in that field, if the variable is empty I get an error. The only way around this that I found is to create a conditional action that asks if the record needs or doesn't need the field and create two different Add record actions.

My question is if there's a way to do a single Add record that encompasses both cases. If the field were a simple string, I can do that with an IF inside a formula. But using an IF with OData, I can put OData in the case the contact should be there, and... what to put when I don't want a Contact field with data?

Regads,
Suggested answer

Michael E. Gernaey 43,417 Super User 2025 Season 1 on at

Like (0)

Report

Add a record with odata.id null

Hi,

So I am going to back you way up because lots is missing and I have to assume and don't like it lol.

You created a table, that has a relationship with Contact yes???

Or someone did, and whomever did, make it business required. So there is no way to ignore it.

That or please show your table/list and the columns and the requirements for it, so I can verify that is the issue.

So if this is a Flow, and you see a Red * then its required and you cannot leave it blank and unfortunately thats the answer. To change the behavior you need to completely remove that table and recreate it and make it either optional or business recommended, neither will require it.

Sucks but :-( thats it.

Community site session details

Add a record with odata.id null

Helpful resources

News and Announcements

Quick Links

Michael Gernaey – Community Spotlight

Congratulations to the May Top 10 Community Leaders!

Announcing the Engage with the Community forum!

Leaderboard > Power Automate

Featured topics

Product updates

Community site session details

Add a record with odata.id null

Helpful resources

News and Announcements

Quick Links

Michael Gernaey – Community Spotlight

Congratulations to the May Top 10 Community Leaders!

Announcing the Engage with the Community forum!

Subscribe to this forum!

Select categories

Leaderboard > Power Automate

Featured topics

Product updates