I'm building up our office template at the moment and have just reached the point of referring to shared parameters.
To date we've always started projects to look at the "company.txt" then, when new wants (&workarounds) come up that might throw the structure of that file out a bit, we duplicate it and make it a "projectXXX.txt" that sits in the local project library.
To date, that's not been a problem - save having to redirect the models to the file - and so far we've never lost functionality and have only had the one instant of an orphaned field (thanks to a partner firm not sharing their editted version of the SP.txt file!)
but it has always struck me how shared parameters can't be harder-fixed to respective models (or vice versa) and was wondering how you lot keep things all in check?
To date we've always started projects to look at the "company.txt" then, when new wants (&workarounds) come up that might throw the structure of that file out a bit, we duplicate it and make it a "projectXXX.txt" that sits in the local project library.
To date, that's not been a problem - save having to redirect the models to the file - and so far we've never lost functionality and have only had the one instant of an orphaned field (thanks to a partner firm not sharing their editted version of the SP.txt file!)
but it has always struck me how shared parameters can't be harder-fixed to respective models (or vice versa) and was wondering how you lot keep things all in check?
Comment