Answered

Could not find a property named - Lookup field API column Data

(0) Share

Report

Posted on by RCSI_SIA_BAH

Hello,

I am actually trying to create a power automate flow and within that I'm trying filter rows using a lookup field. I'm using the logical name of the lookup field in the table being used which in this case is "new_stageid", however, I keep getting a parsing error and the exception name is Microsoft.OData.ODataException: Could not find a property named 'new_stageid'.

So I went into dataverse and found the column and within tools, clicked on API Link to Column Data, however, even from the API call, I am getting the same error saying that it could not find a property named that within the table.

This is a very frustrating error, because I tried many other things but for some reason this just keeps happening with lookup fields, but works fine with regular fields. I can add another action to filter the list but I would prefer to have it in that action itself.

Any clues?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (10)

Answers (1)

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@RCSI_SIA_BAH Is this a polymorphic lookup? If not, try _new_stageid_value in your filter expression

Was this reply helpful? Yes No
RCSI_SIA_BAH 34 on at

Like (0)

Report

@parvezghumra This isn't a polymorphic relationship, however, I did try the suggested and got the same result.

We get the same output when we try to get the API column data from any other table that contains any other lookup from any other table, which is that it is unable to find the property name "Given Logical Name" under the specified table.

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@RCSI_SIA_BAH Can you share a screenshot of the error and of the trigger showing how you have set its properties

Was this reply helpful? Yes No
RCSI_SIA_BAH 34 on at

Like (0)

Report

@parvezghumra
Getting the API Column data from DataverseThe API call response stating that the property name could not be foundPower Automate Trigger using the lookup field logical name to filter (Even the original logical name when used gives the same error)Exception found

I have attached 4 screenshots above, the first one showing the way I get the API column data.
The second one showing the results from the API call stating that the property name does not exist under the table.
The third one shows the trigger action within Power Automate using the fields for filtering the rows (the screenshot is using the suggested logical names, however, using the original logical name provides the same result).
The fourth one shows the exception found within Power Automate that prevents the flow from executing, the full error message is as follows:
Exception parsing new_stageid_value eq '54bf33f3-c120-ee11-9966-000d3a296018' or new_stageid_value eq '067b9dfd-c120-ee11-9966-000d3a296018' or new_stageid_value eq '50e3ab04-c220-ee11-9966-000d3a296018' for attribute filterexpression of callback registration. Target entity: new_appealstage. Exception: Microsoft.OData.ODataException: Could not find a property named 'new_stageid_value' on type 'CallbackRegistration.new_appealstage'.
at Microsoft.OData.UriParser.EndPathBinder.GeneratePropertyAccessQueryForOpenType(EndPathToken endPathToken, SingleValueNode parentNode)
at Microsoft.OData.UriParser.EndPathBinder.BindEndPath(EndPathToken endPathToken)
at Microsoft.OData.UriParser.MetadataBinder.Bind(QueryToken token)
at Microsoft.OData.UriParser.BinaryOperatorBinder.GetOperandFromToken(BinaryOperatorKind operatorKind, QueryToken queryToken)
at Microsoft.OData.UriParser.BinaryOperatorBinder.BindBinaryOperator(BinaryOperatorToken binaryOperatorToken)
at Microsoft.OData.UriParser.MetadataBinder.Bind(QueryToken token)
at Microsoft.OData.UriParser.BinaryOperatorBinder.GetOperandFromToken(BinaryOperatorKind operatorKind, QueryToken queryToken)
at Microsoft.OData.UriParser.BinaryOperatorBinder.BindBinaryOperator(BinaryOperatorToken binaryOperatorToken)
at Microsoft.OData.UriParser.MetadataBinder.Bind(QueryToken token)
at Microsoft.OData.UriParser.BinaryOperatorBinder.GetOperandFromToken(BinaryOperatorKind operatorKind, QueryToken queryToken)
at Microsoft.OData.UriParser.BinaryOperatorBinder.BindBinaryOperator(BinaryOperatorToken binaryOperatorToken)
at Microsoft.OData.UriParser.MetadataBinder.Bind(QueryToken token)
at Microsoft.OData.UriParser.FilterBinder.BindFilter(QueryToken filter)
at Microsoft.OData.UriParser.ODataQueryOptionParser.ParseFilter()
at System.Web.OData.Query.FilterQueryOption.get_FilterClause()
at Microsoft.Crm.ObjectModel.EdmModelEvaluator.EvaluateFilterExpression(String filterExpression, ODataQueryOptions queryOptions)
at Microsoft.Crm.ObjectModel.EdmModelEvaluator.EvaluateFilterExpression(String filterExpression)
at Microsoft.Crm.ObjectModel.CallbackRegistrationService.<>c.<.cctor>b__73_0(EdmModelEvaluator evaluator, String testValue)
at Microsoft.Crm.ObjectModel.CallbackRegistrationService.ValidateInputEntity(IBusinessEntity entity, ExecutionContext context, IFeatureDetailContainer featureDetailContainer)

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (1)

Report

@RCSI_SIA_BAH It should be _new_stageid_value not new_stageid or new_stageid_value. In other words you need to include the leading underscore ( _ ) prefix

The FetchXML Builder tool in XRM Toolbox is a great help. You can use it to build your query using a GUI and then convert it from the underlying FetchXML to other formats like oData query, Power Automate parameters, C#, or JavaScript code. I would highly recommend this. But from what you're describing here, there might be a bug here in the 'API Link to Column Data' functionality

Was this reply helpful? Yes No
RCSI_SIA_BAH 34 on at

Like (0)

Report

@parvezghumra I have tried even with the underscore ad a prefix yet still the results are the same. I will try out the FetchXML Builder tool regardless, but it does seem as you said a bug in the API Column Data.

Was this reply helpful? Yes No
a33ik 3,306 Most Valuable Professional on at

Like (0)

Report

Hello,

I would highly recommend checking Dataverse Rest Builder plugin of XrmToolbox. It should help you build the query you want to build.

Was this reply helpful? Yes No
PowerThomas 277 on at

Like (0)

Report

This is indeed highly recommend. I always have FetchXML builder open when working in Power Automate with Dataverse tables.

Was this reply helpful? Yes No
Verified answer

Fubar 8,346 Super User 2025 Season 2 on at

Like (1)

Report

the API link to Column in the make interface is not correct for lookups. The column for a lookup should be _logicalschemaname_value (https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/query-data-web-api#lookup-property-data)
if you do the API link to Column and then adjust the browser url to what should be the correct column name (_ prefix and _value suffix) - do you get any results? if get a similar error make sure you have published the Table.

Was this reply helpful? Yes No
RCSI_SIA_BAH 34 on at

Like (0)

Report

@Fubar Thank you for this, apparently that was it, I called the API for the column data and adjusted the URL to have the column name as _columnlogicalname_value and within the filter on Power Automate remove the quotes since it is a GUID and it works as it should.

Was this reply helpful? Yes No