RE: [Axapta-Knowledge-Village] Table keeps appearing in USR layer when I sync!!!

[James Flavell]

Title: Message

Thanks Barry,   I was not really clear which was best to be honest but always stayed away form with ID and with your feedback I agree with you.    I always used wihtout the id but then ran into problem whereby I had 2 appl one that had some changes to tables that I wanted to moved into the second appl (which didnt have some of these tables existing) so I did export without id and then imported them into another appl (I guess maybe the import didnt create the tables in the same order as how the user had or maybe there was some other tables in the second appl that had been created and hence table ID already increased...) . Now later I had to take the layer (not xpo) of the second appl and put it into the first appl.   When I did this the ID in the layer was different to the ID in the SQL of the first appl (which was the live system) therefore sync would not complete as SQL and Axapta were disagreeing on IDs of several tables.  So I think if you are mixing xpo and layer 'rebuilding' then you need to be careful and may need to use export with ID IF IF IF IFif you have an SQL database that you cannot wipe out (this was my problem, if I could wipe the SQL then it would not matter)   Thanks for your help James   -----Original Message----- From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Bayliss, Barry Sent: 15 September 2005 07:46 To: Axapta-Knowledge-Village@yahoogroups.com Subject: RE: [Axapta-Knowledge-Village] Table keeps appearing in USR layer when I sync!!!   James,   In my experience it is best NEVER to use the ‘export with id’ option.  As a rule, your development system may contain objects which are not released to the live system, hence the number sequences will be different.   The only time you would consider using the ‘export with id’ is when you refer directly to the objects id.  However, there are a number of functions that can be used to obtain the objects id.  For example,   Using IDs directly             Switch (object.tableID) {             Case     103:                         Xxxxxxxxxx; Break;                         Case     345:                         Xxxxxxxxxx; Break;   }                         Using functions to obtain the Id.             Switch  (object.TableID)             {                         Case     TableNum(EmplTable):                                     Xxxxxxxxxx; Break;                           Case     TableNum(PurchTable):                                     XXXXXXXXXX;                                     Break;             }   James, I am curious why you believe it is better to use ‘export with ID’?         Barry.   From: Axapta[EMAIL PROTECTED] [mailto:Axapta[EMAIL PROTECTED]] On Behalf Of James Flavell Sent: Tuesday, 13 September 2005 9:44 AM To: Axapta[EMAIL PROTECTED] Subject: RE: [Axapta-Knowledge-Village] Table keeps appearing in USR layer when I sync!!!   Thanks for the help,   I managed to work out what was wrong after about half a day!!!   Here it is so hopefully some of you can avoid the pain:   Even with no USR layer (i.e. I deleted the axusr.aod), as soon as I sync it would appear in usr layer. Compare said there is no difference   I realised the table ID in the existing appl was different to the dev system (and hence what was being imported).   I luckly had a backup of the var layer and also had dated all my xpo projects so I could take the older var and import all projects since a given date.  This meant the dev table id were then same as live appl.  After this I copied the new axvar.aod to live appl and was okay.    But this brings up a question I asked long ago, in brief can someone tell me when and when not to use 'export with id' in Axapta? From my experience I am thinking it is always better to do export with id but then again I think if 2 programmers are working on separate systems and bring them together exporitng with id is not a good idea....   Also if this happens again is there any other way to fix it as maybe it would not be possible to create a new var?  I take it tehre are some tables in Axapta that store the table id and name mapping etc that maybe can be changed?   Thanks James     -----Original Message----- From: Axapta[EMAIL PROTECTED] [mailto:Axapta[EMAIL PROTECTED]] On Behalf Of Dyachenko, Dmitry Sent: 13 September 2005 02:07 To: Axapta[EMAIL PROTECTED] Subject: RE: [Axapta-Knowledge-Village] Table keeps appearing in USR layer when I sync!!! Hi James,   It seems like you have a problem.   First of all compare the table on var and usr layers. Is there any difference? What is on the usr layer? Then check utilelements table and try and delete all the record related to the table on the usr layer.   If it doesn’t help, delete the whole usr layer (as well as usp) and try and resync your data dictionary.   Imho, deleting the SQL table won’t help because the problem is in the application.   And make a backup before you start doing these things.   Good luck, man.         From: Axapta[EMAIL PROTECTED] [mailto:Axapta[EMAIL PROTECTED]] On Behalf Of James Flavell Sent: Monday, September 12, 2005 12:06 AM To: Axapta[EMAIL PROTECTED] Subject: [Axapta-Knowledge-Village] Table keeps appearing in USR layer when I sync!!!   Help I need some urgent assistance....   I have a table that is supposedly only in the VAR layer.   When I go into axapta it is only in the var layer but when I sync the table it becomes var and USR layer!!!???   I am rather worried about this, has anyone experienced this?  The sync fails with 'object tablename already exists' and I have to drop the table from SQL but everytime I redo the sync it comes back into the usr layer of axapta....   Thanks james   Sharing the knowledge on Axapta. YAHOO! GROUPS LINKS  Visit your group "Axapta-Knowledge-Village" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.