SharePoint Power Apps ID Field not matching Issue

[kmolmstead]

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.

[BCBuizer]

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):

[kmolmstead]

No, I have only one field named ID.

[BCBuizer]

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

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.

[kmolmstead]

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 · Accepted solution]

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]

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:

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

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:

[kmolmstead]

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.