Is there a simple way to rename a data model name (in bulk) in call procedures?
I'm wondering if there is an easy solution to rename the data model name in call procedures in bulk.
I've just read the best practice with regards to data model names, and it's to bad that during the implementation of BOARD (years ago) we didn't take this into account. While implementing BOARD, the consultant used our company name as data model name. Now we are in the situation that we really want to change the name of the data model, taking into account the best practices, and give it a more general name.
What I did was creating a new data model and restore a backup to this new data model with the wanted name. It resulted into the situation where all our call procedures where still referring to the data model with our company name. Is there an instruction manual available or discussion tread what steps needs to be done (what are the pros and cons) to get this done? What should be taken into account? What is affected by this change and what needs to be adjusted? For example, I'm aware that our capsules should be transferred as well from the old data model (name) to our new data model (name).
Good to know. We only have 1 data model in use, so all call procedures should be renamed to the (one and only) new data model name. Hopefully there is a quick and easy way to do this.
If there is no automated way to redirect the call procedures to the new data model name, should this be the best approach?
Go to "Impact analyses"
- Select from "What" —> Procedures
- Select from "Linked to" —> "Data Reader" and "Procedures"
- In the column "Detail" you can filter on the call procedures (and you can even see in which process step the call procedure is, so very nice!).
From here you have to run through the list of all call procedures and rename them in the procedures?
Really apricate it if somebody knows a quick way to change it, because I never knew that we had a lot of call procedures to a data model. Normally (when I'm building myself nowadays) I don't make a lot of use of the call procedures, but work (if possible) rather with groups instead of a lot of different procedures to call in a sequence (how it's build now). Most of the effected call procedures are not used somewhere else again… I think the implementation partner did it to structure the data load. It's of course a choice you have to make as developer and as long as the name of a data model doesn't change, it was never a issue for us to structure the process steps in different procedures instead of (a long list of) groups in 1 single procedure.
- All Categories
- 1.6K Forums
- 1.6K Platform
- 40 Academy
- 219 Resources
- Board Manual
- 44 Best Practices
- 24 How-To Guides
- 23 Board Advocacy Program
- 124 Blog
- 4 Groups Hub
- 4 About Groups
- Board Beta Program
- 47 Training
- 2 Board Academy
- 15 ILT/VILT Course Catalogue
- 13 e-Learning Course Catalogue
- 4 Academy Forum
- 1K Idea Exchange
- 269 Partner Hub
- 89 Support
- 14 FAQ's
- Customer Support Portal
- 52 Support Articles