Populate Lookup with Null

[jouke]

Hi,

I'm building a flow that should populate some Lookup fields on a record in CDS. However, it is possible that some of these lookups are empty and therefor should be empty. I'm having trouble with this as Flow always expects a valid ID in the lookup. I tried the following expression and replaced null with blank, '' , etc. Nothing seems to work. Any ideas on how to do this? 

if(equals(<Record ID>, null), null , <Record ID>)

Thanks!!!

[efialttes]

Hi!

Did you try with

concat('')

already?

If it does not work, my suggestion is to create a dummy record to represent null scenarios, and add its corresponding ID.

Hope this helps

[jouke]

Thanks for the reply!

Concat doesn't work, it still expects an ID:

"message": "The supplied reference link -- -- is invalid. Expecting a reference link of the form /entityset(key).",

Creating a dummy record might be a workaround, I prefer the field to be empty though... Hope that's possible!

[v-bacao-msft]

Hi @jouke ,

Could you provide a screenshot of the Flow configuration?

I have made a test on my side, if I enter null in the lookup column, the flow runs successfully.

Besides, you could use condition to check if record id is empty, if yes, leave the lookup column blank.

Best Regards,

[jouke]

The flow creates a Contact record from a JSON, see below. It is possible for some lookups, Nationality for example, to be empty. When I try to fill the lookup with the JSON, it throws an error when its null. I tried with expressions as well, but i still get this error:

An error occurred while validating input parameters: Microsoft.OData.ODataException: The 'odata.bind' instance or property annotation has a null value. In OData, the 'odata.bind' instance or property annotation must have a non-null string value.

[v-bacao-msft · Accepted solution]

Hi @jouke ,

As mentioned in my previous reply, if it is not a required field, you could check if the Id parsed in the above step is empty first.

If it is null, you could leave this lookup column blank.

Image reference:

Please take a try.

Best Regards,

[paulbaarn]

Hi,

I realise this is an older reply, but can you tell me which connector you are using? I think this works in the old connector and not in the new Current Environment connector.

Best, Paul

[jouke]

Hi Paul,

I'm using the CDS Current environment connector. 

Seems the only way i get this to work is using @v-bacao-msftsuggestion... But when updating multiple lookups on a record, this is not workable.. Still hoping there's another way 🙂 

[Michaelfp]

Hi!
Today I have talked with Microsoft Support and appear to be fixed. But in my environment still happens. This is something for a low-code platform unacceptable. I have to increase the complexity of my flow because of this. In addition, my flow is getting slow in the designer.

[GringoInMiami]

Same problem still exists in either scenario (including Current Env).

[mreed1]

Spoke with Microsoft in a current ticket (120080424004016) and we received an update that this is not fixed and won't be made available until February - March timeframe. Very challenging when updating multiple lookups!

[Digit89]

You can use the CDS "Unrelate Record" action as a workaround while MS fix the possibility to set a null value.

Reference.