Importing customizations

You load the customization into the customization maintenance window. You don't
run it. You should not open up MES in order to do this.



________________________________
From: CarlH <carl.heeder@...>
To: vantage@yahoogroups.com
Sent: Mon, 9 May, 2011 15:16:47
Subject: [Vantage] Re: Importing customizations


So far, so good. but how do I "verify" after I load the base customization? Is
there a menu command?

I'm going to MES developer, loading the base, then what should I do?

--- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@...> wrote:
>
> This is what I did. Switched to developer mode. Select customization
> maintenance. Select the base for for customization maintenance. Load the
> customization and then verify it. You will be prompted to select the base or
> the customization. Select the customized version. It should then verify
>
>
>
>
> ________________________________
> From: CarlH <carl.heeder@...>
> To: vantage@yahoogroups.com
> Sent: Sun, 8 May, 2011 13:20:05
> Subject: [Vantage] Re: Importing customizations
>
>
> I think I have the same issue but am not clear how you verify one customization
>
> against another? What am I missing? We're on 8.03.409
>
> The error I am getting is:
>
> EpiRadioButton - radSetUp Bound to invalid EpiView
>
> so now I am suspecting that the GUID of some object changed and is now
> referencing a radio button.
>
> Any ideas?
>
> --- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@> wrote:
> >
> > I have found a work around for this.
> > What I did was to open customization maintenance up in developer mode. I then
>
> > verified the customization against itself instead of the base.
> > The issue was with GUID ids of the controls
> >
> >
> >
> > ________________________________
> > From: jckinneman <jckinneman@>
> > To: vantage@yahoogroups.com
> > Sent: Fri, 6 May, 2011 18:40:12
> > Subject: [Vantage] Re: Importing customizations
> >
> >
> > Any chance the environment you developed in is at a different release level
>of
>
>
> > Epicor/Vantage? Some releases have been known to change the GUID of
>controls,
>
>
> > making the references from one release invalid in another. If so you can
> > usually make some hand edits using Customization Maintenance to fix things.
> >
> >
> > --- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@> wrote:
> > >
> > > Hi all,
> > >
> > > I am having some trouble importing customisations. The import is presenting
>
> > > warnings related to missing controls e.g a textbox.
> > > In this particular example I have modified a customisation make to
> > > the Receipt Entry screen in a test environment but upon importing it into
> >live
> >
> >
> > > the extra controls have not appeared on the form and there are warnings
> >present
> >
> > >
> > > in the customization maintenance screen
> > > Is there anyway to import this customisation with the controls present and

> > > working.
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>




[Non-text portions of this message have been removed]
Hi all,

I am having some trouble importing customisations. The import is presenting
warnings related to missing controls e.g a textbox.
In this particular example I have modified a customisation make to
the Receipt Entry screen in a test environment but upon importing it into live
the extra controls have not appeared on the form and there are warnings present
in the customization maintenance screen
Is there anyway to import this customisation with the controls present and
working.

[Non-text portions of this message have been removed]
Any chance the environment you developed in is at a different release level of Epicor/Vantage? Some releases have been known to change the GUID of controls, making the references from one release invalid in another. If so you can usually make some hand edits using Customization Maintenance to fix things.

--- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@...> wrote:
>
> Hi all,
>
> I am having some trouble importing customisations. The import is presenting
> warnings related to missing controls e.g a textbox.
> In this particular example I have modified a customisation make to
> the Receipt Entry screen in a test environment but upon importing it into live
> the extra controls have not appeared on the form and there are warnings present
> in the customization maintenance screen
> Is there anyway to import this customisation with the controls present and
> working.
>
> [Non-text portions of this message have been removed]
>
I have found a work around for this.
What I did was to open customization maintenance up in developer mode. I then
verified the customization against itself instead of the base.
The issue was with GUID ids of the controls



________________________________
From: jckinneman <jckinneman@...>
To: vantage@yahoogroups.com
Sent: Fri, 6 May, 2011 18:40:12
Subject: [Vantage] Re: Importing customizations


Any chance the environment you developed in is at a different release level of
Epicor/Vantage? Some releases have been known to change the GUID of controls,
making the references from one release invalid in another. If so you can
usually make some hand edits using Customization Maintenance to fix things.


--- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@...> wrote:
>
> Hi all,
>
> I am having some trouble importing customisations. The import is presenting
> warnings related to missing controls e.g a textbox.
> In this particular example I have modified a customisation make to
> the Receipt Entry screen in a test environment but upon importing it into live

> the extra controls have not appeared on the form and there are warnings present
>
> in the customization maintenance screen
> Is there anyway to import this customisation with the controls present and
> working.
>
> [Non-text portions of this message have been removed]
>




[Non-text portions of this message have been removed]
I think I have the same issue but am not clear how you verify one customization against another? What am I missing? We're on 8.03.409

The error I am getting is:

EpiRadioButton - radSetUp Bound to invalid EpiView

so now I am suspecting that the GUID of some object changed and is now referencing a radio button.

Any ideas?


--- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@...> wrote:
>
> I have found a work around for this.
> What I did was to open customization maintenance up in developer mode. I then
> verified the customization against itself instead of the base.
> The issue was with GUID ids of the controls
>
>
>
> ________________________________
> From: jckinneman <jckinneman@...>
> To: vantage@yahoogroups.com
> Sent: Fri, 6 May, 2011 18:40:12
> Subject: [Vantage] Re: Importing customizations
>
>
> Any chance the environment you developed in is at a different release level of
> Epicor/Vantage? Some releases have been known to change the GUID of controls,
> making the references from one release invalid in another. If so you can
> usually make some hand edits using Customization Maintenance to fix things.
>
>
> --- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@> wrote:
> >
> > Hi all,
> >
> > I am having some trouble importing customisations. The import is presenting
> > warnings related to missing controls e.g a textbox.
> > In this particular example I have modified a customisation make to
> > the Receipt Entry screen in a test environment but upon importing it into live
>
> > the extra controls have not appeared on the form and there are warnings present
> >
> > in the customization maintenance screen
> > Is there anyway to import this customisation with the controls present and
> > working.
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>
This is what I did. Switched to developer mode. Select customization
maintenance. Select the base for for customization maintenance. Load the
customization and then verify it. You will be prompted to select the base or
the customization. Select the customized version. It should then verify




________________________________
From: CarlH <carl.heeder@...>
To: vantage@yahoogroups.com
Sent: Sun, 8 May, 2011 13:20:05
Subject: [Vantage] Re: Importing customizations


I think I have the same issue but am not clear how you verify one customization
against another? What am I missing? We're on 8.03.409

The error I am getting is:

EpiRadioButton - radSetUp Bound to invalid EpiView

so now I am suspecting that the GUID of some object changed and is now
referencing a radio button.

Any ideas?

--- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@...> wrote:
>
> I have found a work around for this.
> What I did was to open customization maintenance up in developer mode. I then
> verified the customization against itself instead of the base.
> The issue was with GUID ids of the controls
>
>
>
> ________________________________
> From: jckinneman <jckinneman@...>
> To: vantage@yahoogroups.com
> Sent: Fri, 6 May, 2011 18:40:12
> Subject: [Vantage] Re: Importing customizations
>
>
> Any chance the environment you developed in is at a different release level of

> Epicor/Vantage? Some releases have been known to change the GUID of controls,

> making the references from one release invalid in another. If so you can
> usually make some hand edits using Customization Maintenance to fix things.
>
>
> --- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@> wrote:
> >
> > Hi all,
> >
> > I am having some trouble importing customisations. The import is presenting
> > warnings related to missing controls e.g a textbox.
> > In this particular example I have modified a customisation make to
> > the Receipt Entry screen in a test environment but upon importing it into
>live
>
>
> > the extra controls have not appeared on the form and there are warnings
>present
>
> >
> > in the customization maintenance screen
> > Is there anyway to import this customisation with the controls present and
> > working.
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>




[Non-text portions of this message have been removed]
So far, so good. but how do I "verify" after I load the base customization? Is there a menu command?

I'm going to MES developer, loading the base, then what should I do?


--- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@...> wrote:
>
> This is what I did. Switched to developer mode. Select customization
> maintenance. Select the base for for customization maintenance. Load the
> customization and then verify it. You will be prompted to select the base or
> the customization. Select the customized version. It should then verify
>
>
>
>
> ________________________________
> From: CarlH <carl.heeder@...>
> To: vantage@yahoogroups.com
> Sent: Sun, 8 May, 2011 13:20:05
> Subject: [Vantage] Re: Importing customizations
>
>
> I think I have the same issue but am not clear how you verify one customization
> against another? What am I missing? We're on 8.03.409
>
> The error I am getting is:
>
> EpiRadioButton - radSetUp Bound to invalid EpiView
>
> so now I am suspecting that the GUID of some object changed and is now
> referencing a radio button.
>
> Any ideas?
>
> --- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@> wrote:
> >
> > I have found a work around for this.
> > What I did was to open customization maintenance up in developer mode. I then
> > verified the customization against itself instead of the base.
> > The issue was with GUID ids of the controls
> >
> >
> >
> > ________________________________
> > From: jckinneman <jckinneman@>
> > To: vantage@yahoogroups.com
> > Sent: Fri, 6 May, 2011 18:40:12
> > Subject: [Vantage] Re: Importing customizations
> >
> >
> > Any chance the environment you developed in is at a different release level of
>
> > Epicor/Vantage? Some releases have been known to change the GUID of controls,
>
> > making the references from one release invalid in another. If so you can
> > usually make some hand edits using Customization Maintenance to fix things.
> >
> >
> > --- In vantage@yahoogroups.com, Mark Kamsika <m.kamsika@> wrote:
> > >
> > > Hi all,
> > >
> > > I am having some trouble importing customisations. The import is presenting
> > > warnings related to missing controls e.g a textbox.
> > > In this particular example I have modified a customisation make to
> > > the Receipt Entry screen in a test environment but upon importing it into
> >live
> >
> >
> > > the extra controls have not appeared on the form and there are warnings
> >present
> >
> > >
> > > in the customization maintenance screen
> > > Is there anyway to import this customisation with the controls present and
> > > working.
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>