Announcements
I have an Excel sheet that contains the following columns/headers...
Vehicle No (not unique)
Current Mileage
Past Mileage
Mileage Difference
I want to import this to a Dataverse table (which ultimately will be part of a Many to One relationship).
Vehicle No can be mapped to the primary column (by default the logical name will be prefix_name) but setting it as primary column does not affect if the values are unique or not. If you plan to consider it as a unique key, you need to clean first the excel and create an alternate key inside dataverse using the primary column.
Regarding the auto-increment column, which is the purpose? but probably you need to add it before the import if you want the values filled.
hope it helps
@GuidoPreite Thanks for the response and information. I was able to import the data.
I have the following question, but didn't no if this should be a new post. I now have a table VehList (listing of vehicles in fleet). I also have VehInsp (list of inspections performed on each VehNo from VehList).
My question is should the relationship be a Many-One where multiple inspections are related to the One VehNo...or One-Many where One VehNo has many VehInsp (Inspections). Employees will enter the inspection from their mobile device by identifying the VehNo and then providing inspection pass/fails.
if you create a many-to-one relationship from one side it will be a one-to-many relationship if you see from the other side. From your message to me looks like you want to create the same relationship.
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.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 101 Most Valuable Professional
Haque 81
VASANTH KUMAR BALMADI 70
