L.J., I think your dealing with the "deployable application" paradigm a bit wrong. I think of the deployable application is one logical unit. So, I am not sure it makes any sense to move only a form (that is part of a deployable application) from server to server. No more since than moving an Active link, Filter or Menu either. I think you should move the application, not parts of it.
I also suspect that your not exporting the "application" but your exporting the form object(s). The difference is in the admin tool (Tools--> "Export Definitions..."--> To Definition File") vs ( Tools --> "Export Application") . If you look at the two files you will see differences in the format/data. HTH. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 6/21/07, L. J. Head <[EMAIL PROTECTED]> wrote:
** I'm not the migrator guy....but he tells me that in order to get everything over...you must first migrate the form, then the app, then the form to get everything over without any differences....that is unless you have that option enabled then all you must do is migrate the app and it takes care of all of it ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of patrick zandi Sent: Thursday, June 21, 2007 7:50 AM To: [email protected] Subject: Re: Form Permissions Stripped ** What happen's if you do a difference report and then migrate differences only ? On 6/21/07, L. J. Head <[EMAIL PROTECTED]> wrote: > Ok...here is a situation at my current position that I can't understand. > > ARS 6.3 P21 > Server 2003 > SQL 2000 > > You have an existing deployable application on server B. On server A you > add a new form to that same deployable application. If you then import the > new from into Server B the admin tool strips the role permissions because it > is not part of the deployable app...so you now add that new form to the > application...and re-import and all works well...so we have a chicken and > egg situation...we have a deployable application which doesn't contain the > form...and a form that doesn't exist...so we can't add it. We contact > Remedy support about this issue and get the fabled 'functions as designed' > reply...another co-worker found an option in Migrator that tells it to bring > any 'missing' forms over with an application during migration...which seems > to work...but I can't believe they would put you in this catch 22 without a > solution...any suggestions on how this could be done without errors without > having to import things multiple times? > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" > -- Patrick Zandi __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
