Description: It would be great if there was a read-only unique value generated for each entry within a module field group. Right now, there isn't any truly unique value differentiating items within a field group. Who benefits: Mainly developers, but with this new value, more complex features, especially ones that rely on identification, can be built for clients. Goal: Think of this like how the hs_object_id operates in HubSpot objects: this value would be a unique identifying value, which could be used in many of the same ways in HubL. Added Value: Right now, if the code is needing a unique value for these field group items, someone has to be contrived in HubL, like the slug determination of a user-provided value within that field group item, but since that derived value is ultimately determined by a user-changeable value, that supposedly unique value can change. By adding this generated read-only unique value to each field group item, the problem of relying on user-input for uniqueness goes away. Example: Let's say you need to keep track of user progress through a set of groupings in a field group. In this scenario, you will need some kind of unique identifier to determine where the user left off at in going through those items in the field group. Since values within the field group can be changed at will, right now, there's no truly reliable means of figuring out where a user left off, if any of the items in the field group have been modified.
... Exibir mais