Very dumb question - How do you move an element to a different group box?
I couldn’t find anything in the customization guide, and doon’t seem to be able to drag and drop it in the tree view. Cut and paste only seemed to work in the existing group.
I’m going through our Quote Entry Form which we customized in 10.0, and the new fields in 10.2 played havoc on some of the layouts. We’ve got fields in a group box that we created years ago that I’d like to move into the std grpTerritory box.
Cut and paste DOES work, I use it frequently - you just have to know how to make it play nicely.
Cut from Existing Group
Paste into new Group - it won’t be visible because the location pixels are retained from the original object, so the controls may now not be visible)
Alter the location to 0 ,0 which means you can see them again
Drag drop to desired final location
It’s a pain, but it certainly quicker than recreating the controls and all associated method code!
Just curious … But what would a COPY and Paste do? Create an identical control except for the GUID? I assume a CUT and paste retains the original control’s GUID - or is that not the case?
I have found bugs in the EpiViewNotification when doing the Cut/Paste. For all versions I’ve used code to change the Parent GUID on base objects and Customization Management to change in for custom object.
Jose - Thanks! Edited to show it’s now fixed! Here’s steps I followed if anyone else will benefit:
Since I haven’t learned C# yet, I exported the xml, and edited in Notepad++. Doing a find-all for grpCallTag in the xml file, it shows up 13 times. I changed the guid in 2 places.
The first was the <ParentControlKey>, which I changed from the old parent to the new parent. The 2nd place was the <PropertyValue> field under the Parent <PropertyName>.
Finally, I re-imported the customization. All looks right!
Just noticed in the ICE Customization User Guide that we can edit XML in Epicor, so no need for Notepad++ anymore, and we can edit the parent key in one spot. Score for RTM