Patch
May 21, 2020, 7:16am
7
I do not know what the long term plan is. Using a machine generated unique identifier ensures they are unique. If a user assigned name is used some other method needs to be used to ensure the names are unique
UUID = universally unique identifier
The 128 bit number can be mapped to a human readable string which can be used by the software instead however for that 2 way translation to work, the human readable string must also be unique.
If you look where UUID is currently used this is not currently a program requirement. Implementing it means
restricting those field with plain text UUID presentations to only accept unique values,
inform the user when they try to enter a value which the program has …
However at one time Lubos was hoping to eliminate them
In near future, batch create won’t contain any GUID keys. And batch update will have only one key to identify the record. The same goes for custom fields where the custom field will be simply identified by the name rather than GUID key column.
The current implementation is not user-friendly.
1 Like