Customization Warnings after Upgrade

Yahoo Archive
1
Thanks Jen (and Jason),



It's weird because sometimes I will go into the customization, move the
controls and put them back, save then the controls disappear on the next
open.

I tried closing Epicor, go back in, and then the controls are their!
Also, I'll then try to revalidate the customization and there are no
warnings...



I do have one customization, that used UD table views, that seems to be
beyond repair, that I think I will have to rebuild...not looking forward
to that.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Lisser, Jennifer
Sent: Thursday, May 17, 2012 11:40 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Customization Warnings after Upgrade





Joe,
Hopefully others will post to this with better solutions than what I
ended up doing. The "sometimes display" was a big problem for us with
those warnings - inconsistent from day-to-day and user-to-user. I ended
up going into the custom XML in customization mode and making sure the
GUIDs for the parent object were set right (for example, we had added
sheets in many of our screens and the controls were associated with old
GUIDs). Some of them were so tangled I just ended up pulling the old
customization and rebuilt it in the new, starting from the base screen -
2 screens really helped for that! The other thing we ran into was the
LAYOUT object in custom XML. Our part screen had tabs in all sorts of
levels that didn't belong. I deleted the layout object and it fixed the
problem. Of course, I then had to recreate the global personalizations
we have for saved layouts but it was easier than figuring out all those
extra tabs.
Jenn

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





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



We are in the process of upgrading from 9.04.507A to 9.05.700A.

I am testing me customizations for make sure there are not any major
bugs before letting users start their testing.



I'm noticing that most customizations that have custom controls are
generating warnings in the Customization Maintenance screen after
validating them. Most of the warnings are related to setting properties
and the messages are "Can not locate Control on form", "Control not
created...", and "Control is null...".



If I try to open the screen though, the controls will display...most of
the time.

How do you address these kind of warning?



[Non-text portions of this message have been removed]
3
Sometimes you've got just gotta rebuild.

I haven't fired up .700x yet, but Rich Riley gave a presentation at Insights that said that when you force validate a customization in .700x, it will try to clean up that 'lint' (as he called it) of old controls that don't exist anymore.

--- In vantage@yahoogroups.com, Joe Rojas <jrojas@...> wrote:
>
> Hi All,
>
>
>
> We are in the process of upgrading from 9.04.507A to 9.05.700A.
>
> I am testing me customizations for make sure there are not any major
> bugs before letting users start their testing.
>
>
>
> I'm noticing that most customizations that have custom controls are
> generating warnings in the Customization Maintenance screen after
> validating them. Most of the warnings are related to setting properties
> and the messages are "Can not locate Control on form", "Control not
> created...", and "Control is null...".
>
>
>
> If I try to open the screen though, the controls will display...most of
> the time.
>
> How do you address these kind of warning?
>
>
>
> [Non-text portions of this message have been removed]
>
4
Joe,
Hopefully others will post to this with better solutions than what I ended up doing. The "sometimes display" was a big problem for us with those warnings - inconsistent from day-to-day and user-to-user. I ended up going into the custom XML in customization mode and making sure the GUIDs for the parent object were set right (for example, we had added sheets in many of our screens and the controls were associated with old GUIDs). Some of them were so tangled I just ended up pulling the old customization and rebuilt it in the new, starting from the base screen - 2 screens really helped for that! The other thing we ran into was the LAYOUT object in custom XML. Our part screen had tabs in all sorts of levels that didn't belong. I deleted the layout object and it fixed the problem. Of course, I then had to recreate the global personalizations we have for saved layouts but it was easier than figuring out all those extra tabs.
Jenn


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