cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
bfing
Advocate I
Advocate I

Using Display Names vs. Logical Names

I have a scenario where I ClearCollect data from a CDS entity so that I can use it locally within the app.  On a given screen, I have a Gallery to view the collection records, a Display Form to see selected record details, and an Edit Form to input/modify child record data of a related entity.  To drive the functionality, rather than using the Gallery.Selected identifier, I'm using a context variable defined as follows:

 

Gallery.OnSelect = UpdateContext({locCurrentItemRecord:ThisItem})

 

 

After setting up the screen and controls referencing Display Names (e.g. locCurrentItemRecord.Name, locCurrentItemRecord.Level, etc.) and getting the screen to function exactly as intended, I began to work elsewhere in the app.  When I came back to this screen, I saw an "Invalid Argument Type" error at each use of the context variable.  Specifically, the identified field name had the red underline and when you hover over it it says "This identifier isn't recognized".  When I changed the Display Name to the Logical Name, the error clears and the screen continues to function as it did previously.


I am curious what is triggering this change in operation of the screen and the previously functioning expressions?  My understanding is that there is mapping that occurs in the background that permits the use of Display Names.  Is this not the case with collections?  Should I proceed, when using collections, to simply reference the Logical Name the first time, so I don't have to go back and change this?

 

It may be worth noting that I'm supplementing the CDS data on the initial ClearCollect by using the AddColumns.  Thanks in advance.

10 REPLIES 10
v-siky-msft
Community Support
Community Support

Hi @bfing ,

 

I made a test on my side, both DisplayName and logical Name can be referenced correctly by variable.

Though I cannot reproduce your issue, I suggest you use Logical Name. When you go to Variables Tab to see the table stored in the variable, you can find all column names are Logical Name.

Snipaste_2020-04-22_14-37-21.png

Hope this help.

Sik

I had already updated context variables to reference the Logical Names, as I mentioned.  I will continue to do so going forward, as you recommend.  However I'm still not clear on the why it worked previously using Display Names, and then had to be modified to Logical Names.

 

Thanks for the input.

Hi @bfing ,

It could be intermittent CDS connection problems.

Does this issue always come up?

Sik

Within my somewhat limit experience using PowerApps, I don't recall this happening, no. 

 

The first time it happened, I actually changed the context variable name in the few places it was defined, then in the several places it was used while keeping the Display Names.  This cleared all the errors initially.  But eventually (as in, clicking through the app and retesting all the functionality associated with the variable), all the same errors came back.  I also recall them not all coming back simultaneously, but rather 2 or 3 uses of the variable (that I corrected with Logical names) then another 2 or 3 uses a minute later (again correcting with the Logical Name).  Finally, I changed them all to the Logical Name so I could move on.  

 

Since I didn't understand why it was happening, I figured I would post the question.  Thanks again for the interest, let me know if you have any other questions.

Strangely, several more references to collection column Display Names broke again today (these were all previously working fine since before my original post on this thread).  This time however, they were not references to the collection columns through a record stored as a context variable; they were simply direct collection column references.

 

As before, changing to the Logical Name cleared the error.

 

Any feedback as to what may be triggering this change in Power Apps behavior is appreciated.

 

Thanks in advance.

Since I still don't have resolution on this item, I'll continue to document my experience in the event someone can properly explain why this is happening.

 

Today I made a small change to the data source that the collection and context variable reference.  When I subsequently opened the app, there were errors with all the controls that reference the collection and context variable.  Upon investigating further, the Logical Names that I previously had input had been revised back to Display Names.  I modified them back to Logical Names to clear the errors again.

@bfing @v-siky-msft I have a similar issue...

 

I've noticed the app would change the reference from schema name to display name. Whenever I opened the app it would somehow gives me error when referencing the display name so I changed to schema name. 

 

And now it somehow change itself back to display name and gives me the error.

yichingjc_0-1598538898871.png

 

Unfortunately, I stopped getting feedback on this post and I don't have a good understanding of why I was also experiencing these issues.  

 

For me, I simply stopped using Display Names when referencing fields from collections of cached records.  While this works, it was not the solution I looking for.  If you find a better solution or explanation, please share it here.

Django
Impactful Individual
Impactful Individual

Same happened to me last week... in my case a different user opened the Canvas App in his Studio and his references to the internal database name / logical name stopped working:

Django_1-1688997365172.png

These are references to the Account table coming from the Common Data Model and our team did not change anything to the schema of this table.

 

My first thought was that it could be a browser language issue because referencing the language specific display name fixed the error:

Django_2-1688997453114.png

However when my user account would open the Studio, the same errors appeared... while one week earlier that same user account (on the exact same device) would have no issues at all with this version of the Canvas App in the Studio referencing the logical names...

 

Still troubleshooting this one --> somehow it seems that Canvas App sometimes reference the display name and sometimes reference the logical name of Dataverse?

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (2,866)