Environment Source: ARS+AtriumCore+AsstMgmt v7604 sp2 Windows 2008 w/SQL 2008 [all 64 bit] Environment Destination: ARS+AtriumCore+AsstMgmt v7604 sp3
Windows 2008 w/SQL 2008 [all 64 bit] We created a few new attributes in the Source, assigned a $\NULL$ menu to several OOTB attributes and ran SyncUI. We duplicated the effort on the Destination server before importing the overlays of the modified AST forms. None of the overlays would import. SyncUI on the Destination server created some of the custom tabs with different field IDs as well as rearranging the location of several of the attributes. For example, on the Source the tab was 'custom2'...while on the Destination the tab was 'custom117'...where the attributes were the same. So instead of the usual 'custom0', 'custom1', 'custom2', etc. I have 'custom0', 'custom1', 'custom138', 'custom139', 'custom140' or on one I have only 'custom171', 'custom172', 'custom173'. Anyone else seen this issue of mis-matched tab field IDs or the fields being on different tabs (i.e., 'newattribute' on 'custom4' on Source, on 'custom5' on Destination)? And if so, how did you handle it? I just recreated my overlays. Thx, Julie _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
