Once upon a time, in a land far far away, the function library served a very useful function (pun intended). Except the solution workbench was fearful of the little function libraries gaining too much control. At first, the solution workbench (sw for short) simply ignored the little function libraries and wouldn’t help with the migration.
However, Wanda the good witch in this story, ask for and was granted access to allow function libraries to participate in a Solution, thus the little guys could be migrated from one environment to another. Wanda was beaming with pride when the big bad software company enable this Functionality.
Only to have her dreams crushed when she learned sw still had fear is his heart. True, he did include the function library in the solution; however, he slapped a permanent “Read Only” label in the new environment. While Wanda thought at first, “not so bad”, no one should be modifying functions in the production environment anyway.
Wanda began to wonder what would happen in the windy future when Sys Ops copied the production environment over to the Pilot / Development environment. Hmmm, her heart would be crushed again as she would have to figure out how to delete the library and re add it in order to make modifications.
Oh, big bad software company, please tell me it isn’t so and that Wanda didn’t build the solution correctly. That there are indeed ways to modify the functions after being migrated? Maybe there is a fix? Maybe there is an alternate reality of moving back to not including function libraries in the solution.
Well, what would you do if your mother asked you?
