Introduction
In the Venio OnDemand system, field mapping templates are essential tools that allow for the transformation and manipulation of data fields. However, there might be instances where you want to make these templates non-editable to maintain consistency and prevent unintentional alterations by Venio OnDemand (VOD) users.
Here's how you can achieve this by directly updating the system's database.
Steps to Follow
Please note: The following steps involve direct manipulation of the database and should be performed only by a system administrator or someone with a similar level of expertise. Proceed with caution.
- Identify the ID of the field mapping template that you wish to make non-editable. You will find this ID in the `tbl_ep_FieldMappingTemplate` table in your database.
- Once you have identified the ID, you will run the following SQL query on your database:
update tbl_ep_FieldMappingTemplate
set IsDefaultTemplate = 1
where Id =[Id of the mapping template in table tbl_ep_FieldMappingTemplate]
Replace `[Id of the mapping template in table tbl_ep_FieldMappingTemplate]` with the actual ID of your template.
This query will set the `IsDefaultTemplate` attribute of your specific template to '1', thus making it a default template. As a result, other users won't be able to modify it.
Conclusion
Upon successful execution of this query, your selected field mapping template will become non-editable for VOD users. This ensures that your data fields maintain a consistent structure throughout their usage, which is crucial for the integrity and reliability of your data.
Please note that this change is irreversible from the UI. If you want to revert your template to an editable state, you'll have to update the database again and set `IsDefaultTemplate` to '0'.
Remember, these operations are sensitive and should be performed with due care to avoid any unintended consequences.
Disclaimer: Always ensure to adhere to your organization's policy and procedures when directly manipulating the database. When in doubt, consult with your IT department or database administrator. It's also recommended to perform a backup before making changes to the database.
Comments
0 comments
Please sign in to leave a comment.