- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10 hours ago
Hi Team,
I am facing an issue while creating fields using Catalog Builder.
When I create a field with:
Type: Display Label / Rich Text
the system creates the variable with:
Question = (Empty)
Field label = Empty
Type = 32 value
I want to understand a few things regarding this behavior:
Is this expected behavior for Rich Text / Display Label fields in Catalog Builder?
- Is there any alternative or recommended way to create these fields properly?
Will this field remain in the same state permanently, or can we edit/change it later like normal catalog variables?
- If we migrate this through an Update Set, can this create any issue in another instance?
Has anyone faced this issue before?
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10 hours ago
Hey There,
Yes, this is expected behavior for Display Label/Rich Text fields created through Catalog Builder. These types of variables are mainly used to display information or formatting on the catalog form rather than collect user input, so the system often creates them with empty Question and Field Label values while storing them internally as type 32. You can still edit these variables later and update their content or properties, although some fields may remain blank because they are not used for this variable type.
In most cases, migrating them through an Update Set will not cause issues as long as all related records and dependencies are captured properly, but it is always recommended to test the migration in a lower environment before moving to production.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10 hours ago
Hey There,
Yes, this is expected behavior for Display Label/Rich Text fields created through Catalog Builder. These types of variables are mainly used to display information or formatting on the catalog form rather than collect user input, so the system often creates them with empty Question and Field Label values while storing them internally as type 32. You can still edit these variables later and update their content or properties, although some fields may remain blank because they are not used for this variable type.
In most cases, migrating them through an Update Set will not cause issues as long as all related records and dependencies are captured properly, but it is always recommended to test the migration in a lower environment before moving to production.
