cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
kmolmstead
Regular Visitor

SharePoint Power Apps ID Field not matching Issue

I have a SharePoint list I created from a .CSV import from a MS Access database we are moving away from (New AF Policy). The ID field in SharePoint and the Title Field in SharePoint visually match. However, if you look at the image, I created a collection from the same List and the right side is what I got returned ID=1875 Title=1897.
My original .csv file only had 1878 rows which does account for the difference between 1875 and 1897. 
But here is my Question. The ID field is the autogenerated ID when the file was imported. Why would it show 1875 in Power Apps, but 1897 in SharePoint, the same for the both the correspond fields in SharePoint, at least visually. It shouldn't, it should only be 1875 for this record for the ID field because that is the maximum number of records imported. The Title field which holds the legacy ID from MS Access. There were no deletions, changes or modification to the list to cause this discrepancy.  On Import I tied the legacy ID to the "Title" column, knowing SharePoint would assign an ID field and populate it as each record was added.
I thought I could use the new ID field, I mean visually they are the same. But Power Apps somehow is returning something else, that cannot be seen in SharePoint.
What is causing this and how can I change the behavior?
More Info: The original .CSV files was missing 22 record numbers and matches what I stated above. While the last student in the List has a legacy number of 1900, the stored value should have only been 1878 in the ID Field. In my example above I am using the 4th from last record because that was easiest to display together with the field names visible.
Also I discovered I have an ID and Title field in the list view, however, in List Settings I only have ID, no Title field. The Title and ID field in the list view both act like a "Title" field, you can only rename. This could mean That by importing a field labeled ID from the CSV somehow confused SharePoint and the ID Field and the Title Field are one in the same, and the Real ID is not visible in any form, but still accessible to view in Power Apps. Further Supporting that theory, in Power Apps, when I reference this as a DataSource, I have the choice of ID or 'ID (Title)'. ID returns the 1878 number, 'ID (Title)' Returns the 1900 number. Does that make any sense?

More testing Data. I uploaded the .csv file again and it behaved the same way. This time However I did not rename the Title Field to ID. But when I pulled up the ID field, again they visually matched. I'll upload the xlsx version of the csv file you just have to save it to .csv on your side. Maybe you can mess around with it on your side and see what you get. There is no personal information in the file anymore.

1 ACCEPTED SOLUTION

Accepted Solutions
kmolmstead
Regular Visitor

Okay Third test of what is going on. I think I solved what Happened. Basically, since my source data had an ID field already in it, The Import gave me an ID field that matched the Title where the Legacy ID was going to be stored, and visually took the place of ID in List View, but not actually. The lesson is don't import data the uses the names of the key data columns in SharePoint. 

What I did was change the field name in the original source file to "ID_Legacy" before I imported, now I have three columns of data and the value for the last record are: "ID_Legacy" =1900. "Title" = 1900, ID =1878. So I think it is a SharePoint Display Issue when there are conflicting names to the ones that are required for all SharePoint lists like the ID field. So, in my original two the actual ID field is hidden in the list view and cannot be made visible in SharePoint, but is still available to the inner workings of the list as the actual ID field. 

That would explain why now I have three fields, with two exactly the same. I only imported the "ID_Legacy" field as the "Title" field, so really there should only be one field with the data in it. But I guess if you are building the list for compatibility, you might still need your references to the "ID_Legacy" field by that name, instead of "Title". So, the import process made two identical fields named differently? My speculation at this point, but is supported by the tests I made.

Any thoughts?

View solution in original post

7 REPLIES 7
BCBuizer
Multi Super User
Multi Super User

Hi @kmolmstead ,

 

By any chance, do you have two columns in your SharePoint list with ID as the display name? This is easily verified in the List Settings in SharePoint.

 

By default this should not be possible, but with a hidden space it actually looks the same, for instance (the left column name has a space):

BCBuizer_0-1715199996278.png

 

 



Did you like my post? Please give it a thumbs up! Did I resolve your issue? Please click Accept as Solution to close the topic and so other members of the community can find solutions more easily.

No, I have only one field named ID.

BCBuizer
Multi Super User
Multi Super User

Hi @kmolmstead ,

 

I just quickly checked and actually the SharePoint native ID column is not showing in the list details. The fact that it is showing for you means you have two columns called ID. 

 

The thing that triggered me to look was the given type of column in your screenshot: Single line of text

 

BCBuizer_0-1715254777773.png

 

The native ID column is of type Number.

 

To make it easier to distinguish between the two, consider renaming the Text type column to IDText.



Did you like my post? Please give it a thumbs up! Did I resolve your issue? Please click Accept as Solution to close the topic and so other members of the community can find solutions more easily.

Remember I renamed the Title field to ID, which is why the ID field is Text. I uploaded the xlsx version of the csv file. I have attached the file "Available Columns in List View" for the second attempt that behaved the same way. So, you can see there is only one ID Column and in this case one Title column. There is no other ID field available to show. And I did not change this list in any way after I imported it, except to show ID and elevate it to the first column. Also I attached the Screenshot "List Settings2". On That image you can see I mysterious only have the ID field and not a Title Field again just like the original. Oh, add if you count the rows in the excel file there are only 1878 rows to be imported. Again the ID field having 1900 is weird, right?
I have attached the Excel File for the .csv file to the original post, since I cannot upload that one directly. Since I repeated it, you should also be able to repeat it and then with your own eyes, see what is happening unfiltered by me, per se.

More Information: I built a Power Apps Screen that displays the problem, and why it is so confusing when looking at the list data directly in SharePoint, List View, see file "Power Apps Both Data Sources Example". I made the image so you could see the DataSources in the left pane, as well.
There are two sets of 4 boxes, one for each DataSource.
The Longer text box boxes have the formula for the lower box, returning the Class ID, all responses are correct, except the ID field uses the 1878 number not the 1900 the List view of the ID displays for the Original DataSource. The Lower 4 boxes are for the New DataSource, same as above.

However, what I find interesting is that the second DataSource already acts like the first one, without me physically reassigning the "Title" field to ID, which I did in the original one.

kmolmstead
Regular Visitor

Okay Third test of what is going on. I think I solved what Happened. Basically, since my source data had an ID field already in it, The Import gave me an ID field that matched the Title where the Legacy ID was going to be stored, and visually took the place of ID in List View, but not actually. The lesson is don't import data the uses the names of the key data columns in SharePoint. 

What I did was change the field name in the original source file to "ID_Legacy" before I imported, now I have three columns of data and the value for the last record are: "ID_Legacy" =1900. "Title" = 1900, ID =1878. So I think it is a SharePoint Display Issue when there are conflicting names to the ones that are required for all SharePoint lists like the ID field. So, in my original two the actual ID field is hidden in the list view and cannot be made visible in SharePoint, but is still available to the inner workings of the list as the actual ID field. 

That would explain why now I have three fields, with two exactly the same. I only imported the "ID_Legacy" field as the "Title" field, so really there should only be one field with the data in it. But I guess if you are building the list for compatibility, you might still need your references to the "ID_Legacy" field by that name, instead of "Title". So, the import process made two identical fields named differently? My speculation at this point, but is supported by the tests I made.

Any thoughts?

BCBuizer
Multi Super User
Multi Super User

Hi @kmolmstead ,

 

When trying to create a new list using the file you provided, I don't have the option to import the ID column, probably exactly for the reasons above:

BCBuizer_0-1715284048910.png

After changing the column name to ID_Legacy I am allowed to import it:

BCBuizer_1-1715284463609.png

 

The result is as you describe, with the Title column and Legacy_ID columns containing duplicate date, but this can easily be fixed by deleting the Legacy_ID column from the SharePoint list.

 

The difference in values between the ID and Title/Legacy_ID columns can be explained by some missing values in your file:

 

BCBuizer_3-1715285157847.png

 



Did you like my post? Please give it a thumbs up! Did I resolve your issue? Please click Accept as Solution to close the topic and so other members of the community can find solutions more easily.

On my side the ID Field is void of anything first, but you can also select "Do Not Import" which I did not select because I wanted that data in there, so I left it Empty. See attached image, I hit next at that point. This ultimately became the Title field by default because it was the left most column, but then also was the duplicate ID field created, and then that is where the problems ensued between the actual key for the list and the visible ID field for the list liked to the Title Column.

 

I already knew the missing values because I tracked them down to validate the data from both sides.

Thank you for the validation of the issue. the lesson being do not use dedicated field names SharePoint uses.

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

Users online (441)