Power Platform Community Forum Thread Details

When working with the CDS current environment connector it's common to get Resource not found for the segment errors when processing a flow that is mapping values from CDS lookup fields.

The resolution I see posted in the forums is to wrap your field like so,

accounts(FieldName) where accounts is the internal name of the field within the CDS - This can be a pain to locate.

The issue I am seeing with this approach is when you have a null value the flow fails as it will result in acccounts() which creates the failure. "The supplied reference link -- accounts() -- is invalid. " Causing the whole flow to fail.

I been testing out the follwoing solution to fix this however I have to ask what others are doing? This does not feel like a scalable approach. Why is this connector requiring this? I have some flows that have 5-7 fields that I have to hardcode this procedure which clearly is bad practice.