
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2018 12:03 PM
I have a bunch of variables that I need to put on multiple incident record producers. These variables map to fields on the incident table. I thought I would create this in a variable set but there seems to be a client script that is removing map to field checkbox when I try and create the variables. Is it not good practice to use a variable set on record producers that map to fields? Or is there a way to setup the variable set so map to filed is available when I create the variables in the variable set?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2018 01:02 PM
Brian, its worth noting that the "map to field" checkbox really doesn't do anything other than populate the variable name field with the field selected. The real magic with variables and populating data in the "produced" record is to make sure the name matches a column name in the table associated. This checkbox didn't exist in early versions of SN and the old school method was to match the name value.
So back to your question of wanting to use variable sets for record producers, absolutely it is recommended so you don't have to maintain as many variables. Again just make sure the name attribute on the variables match the incident column name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2018 05:35 AM
Thanks Michael for the clarification. I would much rather do this then have to disable all client scripts. My main reason for asking about best practice was the confusion that came with not being able to map field. It’s good to know that all I have to do make sure the variable name is the same as the field name.