duplicated component IDs with new function
complete
D
Duncan Idaho
We are seeing duplicated component IDs be created if the formula relies on fields that end up blank.
Example formula:
{{location}}[space]{{custom1}}{{custom2}}###
{{location}} = RM1
If the custom fields are blank, the ### are all 001 still resulting in "RM1 001" on many items. This throws an error if we try to edit the product in any way, forcing a manual change (or populate the custom fields which usually we do in final engineering not specification). The problem of course is if the component ID is regenerated it reverts to "RM1 001"
Client version 17.19.3767.0
N
Naresh Nichani
complete
N
Naresh Nichani
Duncan Idaho - We have this issue. Please install latest v17 client
Version 17.19.3770.0
D
Duncan Idaho
Naresh Nichani: I can confirm this resolved the issue. Thanks!
N
Naresh Nichani
Duncan Idaho - We are working on a fix and will let you know when ready. This is a bug.
K
Kevin Frye
Help us understand what you think should happen when you choose an invalid component ID format?
D
Duncan Idaho
Kevin Frye: At the very least, the number should increment so its RM1 002, RM1 003 and so forth. Prior to v17 if the custom field was empty it would increment the number as I just described - but v17 doesnt. At the very least it wouldn't end up with duplicate component IDs.
We fill in the custom fields during drafting to generate component IDs - but dont usually do all of that when just creating initial quotes.