We have a client that does a lot of custom one off work, and they often reuse the same inventory ID, so they do not have to create 100000 inventory id that they will never use. They are using estimates, so everything gets built out to meet the needs of their customer, but when they go to add it in to the project, it will not allow for duplicates on the project task.
They don’t really want to create multiple project tasks, as it duplicates a lot of their work flows. Ideally we would be able to utilize configurations, but configurations and estimates don’t play nicely, especially since there are a lot of outside processes and unknown charges that they need to then flow down.
The workaround that they have come up with is to have duplicate inventory ID (remove and replace1, remove and replace 2, etc) so that they can add everything to the project task and group everything together.
Not ideal, but better than creating a bazillion part numbers.
