FORM_TAG
When data is saved in dat.data_cells there is no way to tag the records with a value. The only way to do this is to make an object and save the object values with the records. FORM_TAG allows each record to be tagged with a unique value when saving data.
This topic contains the following sections:
Implementation
A new parameter, FORM_TAG, has been added to PARAM. This parameter is saved in the data table when data is saved in Bizview. The parameter is also used when records are delete in the data table. The column in the data table is called form_tag nvarchar(50).
There is a text box for the FORM_TAG parameter in the 'Data Dimensions' category in the Template Design right panel. To the right of the text box, you can click to show all unique form_tags that are currently saved in the database. Remember that there could be more form_tags defined in other templates, but they will not be shown in this list, as long as no values have been saved to the database from that particular template.
Saving the Template
It is best practice to set the FORM_TAG initially when you design a new template because it can be difficult to change later when users have started to save values in the database (view issues below).
Issues
Due to the fact that FORM_TAG is used when getting and saving values, there are some issues you need to understand.
If you set a FORM_TAG in a template and values already have been saved to the database, these values will NOT be retrieved when opening the form. When the FORM_TAG has been entered, a criteria is added when reading the data table (and form_tag = ‘<FORM_TAG>’). Since old values don’t have any form_tags, they will not be fetched. The same behavior will occur if you change a FORM_TAG from one value to another, old values with the old FORM_TAG will not be retrieved.
If you want to add a FORM_TAG to a template and data already exists in the database, there can be two cases. Either you already have an object you use to tag the data and want to change this to FORM_TAG, or, you haven't tagged the data with an object but want to do this in the future.
A "TAG" -Object Exists in the Template
If a “TAG”-object exists in the template you should move the object value for the “TAG”-object to the FORM_TAG parameter. This is best done with an update in the data table.
After the updated is executed, you can remove the FORM in PARAM in every template that uses it.
The Existing Data has no "TAG" -Object
It's a little more complicated to update the FORM_tAG if the saved data doesn’t have any specific object values that you can move to FORM_TAG. First, you must decide which criteria to use to get the correct data to update. For example, if it’s enough to filter out a specific CLIENT, VERSION, VALT, and CURR, you can execute this update:
updatedc set dc.form_tag='<TAG_VALUE>'
from <data table> dc
wheredc.client_id='1'
anddc.version_id='BU2013'
anddc.valtype_id='BELOPP'
anddc.currcode_id='SEK'
You should also include some objects in the criteria and do a join towards the dim table.
Remember to make sure you update correct values. You should do a select with the joins before you do the update.