I have a situation whereby users have the option to export the data from a module, adjust the relevant cells & then import the same CSV file to the module.
There is an issue with 2 line items that have Time Period as the format. When they are exported the format in the CSV is 'MMM-YY' rather than 'MMM YY' & if you upload the CSV without re-saving it then it will not remove the data in those fields. If you open the CSV, save the file (even without any changes) & then upload it will fail on those Time Period cells & delete the data that is currently in the module
I'm thinking with this current setup, Users would export the data, open it and then need to change the values in those cells to 'MMM YY' & also add the new data in the same format otherwise it will delete data as above
I know that I could create a date line item & map the data into this & reference the Time Period line item to this but that seems like a unreasonable workaround
Do all the data manipulation/entry in Anaplan. Don't make users export from Anaplan, edit csv's and import back in, this can be done better in Anaplan. It's not best practice and will not scale well as a process.
What is it the users are doing, I think we're missing that context? I assumed from reading they were editing data, which could be done as effectively in Anaplan; especially if the data has come from Anaplan and needs to go back in to Anaplan. Maybe the Excel Add-In can meet requirements, as a bridge between having data in Anaplan and editing it externally?
Expand on your use case and we, as a Community, can try to offer some practical advice.
The date format, if exported as Months from Anaplan will have the "MMM YY" format, in Excel it may look like the MMM-YY format. If the CSV is saved with the format MMM-YY it will not import to Anaplan as the import 'match name' feature expects "MMM YY". So if this is the case ensure it has that custom format in the source file. Or stick to full dates...