microsoft / microsoft/Power-Fx
[Tabular Connectors]: import N:1 as tabular
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.4k
- Forks
- 358
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 3
Description
For CDP, Power Apps imports N:1 fields as scalars, not relationships.
Power Fx code should do that too to be consistent with Power Apps.
So this should work against a Salesforce table:
Filter(Opportunities, StartsWith(ThisRecord.OwnerId, "your_user_id_here"))
Where OwnerId is a N:1 lookup field. Because OnwerId is imported as a scalar (string) value and not a record.
This is different than Dataverse, where N:1 gets imported as a record.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the tabular connector import handling for Salesforce N:1 lookup fields and compare it with the CDP/Power Apps and Dataverse behavior described here. Done means OwnerId is imported as a scalar string for Salesforce so the shown Filter and StartsWith expression works, while Dataverse N:1 fields remain records.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100