I would expect modifications to the roles to cause issues until those were synced for the DA and the form on both servers.
Unfortunately, I get import error messages related to role stripping when attempting to use Admin to Import forms that are part of a DA, even though the form is already on the Destination server with the same roles as the Source server. Do you get those errors, too, and ignore them? If not, I'm glad it's working for you, but it isn't for me. :( Rick P.S. If we had an ARSList award for the worst Remedy application, Migrator would get my vote. In fact, I would name the award after it. Yes, there have been other poor efforts, but at least those have been improved or retired. On 9/25/07, L. J. Head <[EMAIL PROTECTED]> wrote: > > ** That's what I have been able to do in the past yes. Now...if you are > adding roles to the application you should add that data to the Roles form > before moving the changed form to ensure that nothing gets stripped > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rick Cook > *Sent:* Tuesday, September 25, 2007 11:39 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Migrating/Importing forms from Deployable apps > > > ** OK, let me see if I have it now. What you're saying, L.J, is that if > the form that resides within the DA already exists with the proper DA roles > on the destination server, that I don't have to redeploy the application to > update that form? That importing the form normally will allow the role/form > relationship to continue as it was? > > Rick > > On 9/25/07, L. J. Head <[EMAIL PROTECTED]> wrote: > > > > You almost got it....move form, move container, re-move form. This has > > been > > one of those 'trial and error' things...the problem lies > > here...container A > > knows that form is a member of it...if you just update the > > container...the > > container b can't say that the form is a member of it because the form > > doesn't exist....but if you move the form then the container denies > > ownership (in a manner of speaking)...so the form must first exist on > > server > > b for the container to accept ownership...then you re-import form onto > > server b and the container no longer balks about it not belonging to > > it...so > > it lets you import with the permissions you have set. > > > > _____ > > > > From: Action Request System discussion list(ARSList) > > [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook > > Sent: Tuesday, September 25, 2007 10:33 AM > > To: arslist@ARSLIST.ORG > > Subject: Re: Migrating/Importing forms from Deployable apps > > > > > > ** > > I think I get it, but let's see. So I import the subset of form(s) from > > the > > DA(s), which strips the Roles from the forms. Then just importing the > > blank > > application container(s) restores those roles to the forms? Is that > > documented somewhere, or is this a little gem from your own research and > > > > analysis? > > > > Rick > > > > On 9/25/07, L. J. Head <[EMAIL PROTECTED]> wrote: > > > > ** > > I'm not talking about an "Export Application"...I'm talking about go > > into > > applications, right click on the application in question, export to def. > > This will generate a def file similar to just a form export but of the > > application instead....not all of the definitions of the app along with > > data, blah blah blah. Do you get the difference? Oh...and BTW...if you > > use > > Migrator there is a switch somewhere that tells it to migrate the app > > first > > (same part I'm talking about) and then the form so that everything is > > updated properly including permissions > > > > _____ > > > > From: Action Request System discussion list(ARSList) [mailto: > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
