web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / addColumn of related e...
Power Apps
Unanswered

addColumn of related entity

(0) ShareShare
ReportReport
Posted on by 482

Hi All

 

I'm trying to add a column of a related entity. In this instance from a custom entity to the systemuser to retrieve the 'entityimage_url' field. I can achieve it by adding a linked entity and then the addColumn method, but this creates an outer join filter that causes problems when I try to filter the control. Is it possible to just add the column? I can already retrieve other columns from the systemuser table because the relationship exists, just not this column.

 

Thanks for any help on this!

I have the same question (0)
  • skoofy5 Profile Picture
    482 on at

    Just to tease out my problem a bit more...

     

    If I use the following code:

     

     

     const userLink = {
     name: "systemuser",
     from: "systemuserid",
     to: "a1a_assigneduser",
     linkType: "outer",
     alias: "assigneduser",
     };
    
     context.parameters.workflowDataSet.linking.addLinkedEntity(userLink);
     context.parameters.workflowDataSet.addColumn("entityimage_url", "assigneduser");

     

    The column is added successfully, but the following filter is added that stuffs up filtering:

    skoofy5_0-1607392242843.png

     

    My workaround is to add a dummy column from the related systemuser table, retrieve its alias and then use that to add my column like this:

     

     const linkedEnts = context.parameters.workflowDataSet.linking.getLinkedEntities();
     const systemuserTable = linkedEnts.find(x => x.name === "systemuser")
     context.parameters.workflowDataSet.addColumn("entityimage_url", systemuserTable?.alias);

     

    I have to do this because the alias isn't 'systemuser', but some random guid that changes on deployment - it would be great if it wasn't. This workaround creates a bug when filtering - when I expect 5 records to be returned the totalresultcount will be accurate, but it will return a full 'page' of data regardless. In my instance that's 50 records as seen below.
    skoofy5_0-1607399886542.jpeg



    Anyone have a better solution?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 542 Most Valuable Professional

#2
Haque Profile Picture

Haque 206

#3
Kalathiya Profile Picture

Kalathiya 201 Super User 2026 Season 1

Last 30 days Overall leaderboard