Contents
The main caveat was that one of the lists had a lookup column pointing to the other list as well as a projected column. We finally decided to use the OOTB ‘Save list as template’ functionality since it brings overall customizations (views, new columns, etc).
One of the easiest things is to simply start educating your users in On Demand reporting. To me that means, they look at the same page their customer looks at. Code handles it all so there’s no exporting to excel in the first place. I have solved both of these issues.
How can I export a list of names in Excel?
This list has a few lookup columns to pull names from our client and personnel directories. It also pulls what appears to be the Record ID along with the value into the excel. I cannot have these export along side the names. Issue 2: With the same list above, I am having issues getting the columns to export in the proper order in the excel.
I have a SharePoint list I have exported to excel. This list has a few lookup columns to pull names from our client and personnel directories. It also pulls what appears to be the Record ID along with the value into the excel. I cannot have these export along side the names.
Can a lookup column reference the same list?
A lookup column can also reference data in the same list (in which case we call it a self-lookup). In order to put this into perspective, let’s say that I have a resource list that lists all my vehicles.
Can a file be moved from SharePoint to SharePoint library?
This is unlikely to happen when moving a file from your personal files (which do not currently support metadata) to SharePoint sites, but can happen when moving files between SharePoint libraries or sites with mismatched columns.
First, it is important that the associated list (Employees) exists before the migration of the list (Vehicles). This will ensure that the column can be migrated. Secondly, the values in the Sales Representatives list also need to be the same at the source and at the destination.