You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
ResolveObjectPath always returns null
To Reproduce
Create a model with a Dates table and a Date column
run c# script ```ResolveObjectPath("Model.Dates.Date").Output();````
See output shows null
Expected to return the column found
Expected behavior
Expected to return the Dates[date] column found
Observed behavior
null returned
Application specifics
Tabular Editor 2.X version: v2.17.2
Semantic Engine used: N/A
Model Compatibility Level 1500
Additional context
This used to work fine but not sure when in the last couple of years exactly when it broke as the affected code is not regularly run on our system
The text was updated successfully, but these errors were encountered:
Yes, Model.T.Dates.C.Date works but this presents the code with a new problem - I don't know implicitly whether it is a Column or a Measure being referred to (and I didn't need to know).
What was the ambiguity that this was to resolve? It doesn't seem possible to have a measure and a column in the same table with the same name.
Any chance of providing a backward compatible version that will work as the previous one did (accepting that if it gets a conflict it will exception?). I guess the alternative is that I would need to try both T.X.C.Y and then if null returned try T.X.M.Y ..
A hierarchy on a table can have the same name as a measure. Partitions on a table can have the same names as columns, measures and hierarchies. Perspectives can have the same names as tables, and so can roles, etc. etc.
When there is no ambiguity, I guess we can support both path formats in calls to ResolveObjectPath(), however we will have to stick to the new format when calling GetObjectPath().
Describe the bug
ResolveObjectPath always returns null
To Reproduce
Expected behavior
Observed behavior
null returned
Application specifics
Additional context
This used to work fine but not sure when in the last couple of years exactly when it broke as the affected code is not regularly run on our system
The text was updated successfully, but these errors were encountered: