I’ve used the “Duplicate Tasks” action from the dropdown and it works great. If a task needs to be broken up, this is my go to action. Working on reporting though, we’ve noticed that duplicate tasks are also duplicating the “Task ID”. This is creating issues in reporting where a Task ID is expected to be a unique identifier. The Task ID is not one of the selections in the checkbox list while duplicating, but it seems it is happening by default. I can’t think of a good reason to not create a unique identifier here - anyone else having this issue?
The Task IDs are actually not identical - the situation is that Excel is unable to display the entire ID due to rounding issues.
Here’s a thread that discusses this situation:
The key takeaway from that discussion is:
Workaround: Google Sheets can easily open the export and doesn’t round the numbers. You can then download as .xls and open in Excel.
I do see that if I open the same CSV in Google sheets I get a different last digit, but that digit is a zero in Excel. It is either rounding down always or replacing the last digit with a zero in Excel. When I expand the sheet in Excel, I can see that all the last digits are zero. That tells me that we are somehow dropping the last digit and replacing it with a zero in Excel. Any ideas on how to avoid that?
I did figure out a way to do it - not sure if this is the only way but it worked.
Instead of just double-clicking the CSV to open it in Excel which causes Excel to assume the ID column is numeric, which causes it to lose the last digit because it can’t handle numeric values that large, do this:
- Open Excel, select New for a new blank workbook.
- Go to the Data tab; select Get & Transform Data > From Text/CSV
- Browse to and select your exported CSV file and click Import.
- In the resulting window, drop down Data Type Detection and select Do not detect data types. (This step is the key to the whole thing.)
- Click Load. Voila - your IDs are present in their entirety.
Ok that works and keeps me out of uploading to a separate program. I’ll need to setup the headers in the first row again, but the data is all there. Thanks!
@Phil_Seeman when testing this I noticed that IF one was to edit/double-click a value in the Task ID column the issue gets re-introduced and the 16th character as a zero reappears. The fix to this would be to change the format of this column to be TEXT instead of GENERAL.
Another way to do this, if you have access to Power Query Tools, is described in this post: