of the
If you are building your Flows from solutions and connecting to Common Data Service, you should use the CDS (current environment) connector.
When you do, if you populate lookup fields, you might get a “resource not found” error message.
If you get this error, like I did, you are probably just putting the guid of the record in the lookup field. You need to also include the entity name in your reference.
Once you do, your lookup field should populate properly. Thanks to David Yack and Antti Pajunen for this tip.
Cover photo by Wesley Pribadi
From my findings so far, this is specifically the plural version of the entity schemaname. So, if you have a custom entity, it can be confusing.
Ex: A custom activity entity called “Research”. Schema name is xxx_Research. This fix in a Flow would need xxx_researchs(record guid)
could you give a demo?
Amazing!
Thanks to this comment I could finish a Flow in which I had been struggling for around 2 hours.
Greetings from Colombia.
How to set null value to a lookup field using the CDS (current environment) connector?
don’t know bro i am also waiting for it for very long time. Read several blocks but no use
If setting it to
nullstill does not work, there is always Disassociate action that can be used to clear the lookup value.Go to expressions and type null and click ok
User unrelate a row aciton
I had a little confusion!
The guid is string type,
Can I set the lookup field like this?
eg:
campaigns(Record Guid ) — Record Guid got from powerapps request params
or
campaigns([{id:”id”,”name”:”record name”,”entityType”:”entity logicName”}])
Wow. How very Microsoft of them to make it behave that way in one version of the connector but entirely differently in the other. Oh and to document that behavior so well to boot.
[…] https://crmtipoftheday.com/1311/use-entity-name-in-flow-lookups/ […]
Amazing, thanks!
I work with a lot of custom tables and lookup fields: does this trick work follows all english plural rules like -s, -es, -ies?
For example i have a schema name “ChecklistStatus”… should it become “checkliststatuses”?