tag:blogger.com,1999:blog-4889748320010274206.post1837778610649170568..comments2024-03-20T00:45:30.946-04:00Comments on AX WONDERS: Deploying Customizations between AX 2012 EnvironmentsAxWondershttp://www.blogger.com/profile/01901411966215366187noreply@blogger.comBlogger21125tag:blogger.com,1999:blog-4889748320010274206.post-20003727003802428252013-03-12T05:57:34.028-04:002013-03-12T05:57:34.028-04:00Can anyone tell me prelive or Staging environment ...Can anyone tell me prelive or Staging environment is need in Ax 2012 implementation<br />If so may i know the reason for that..<br />Anonymoushttps://www.blogger.com/profile/09787676633207185311noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-65362452194883939322013-03-12T05:56:07.588-04:002013-03-12T05:56:07.588-04:00Can anyone tell me whether Pre live is needed a pr...Can anyone tell me whether Pre live is needed a production environment<br />if so may i know the valid the reason for that????<br />Anonymoushttps://www.blogger.com/profile/09787676633207185311noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-1761970207884550642012-12-06T07:26:07.771-05:002012-12-06T07:26:07.771-05:00Hi there!
Try deleting all transactional data. Yo...Hi there!<br /><br />Try deleting all transactional data. You have some transactions somewhere that are linked to those main accounts. <br /><br />If you write code and/or anyone who does, check the following and just create a job in AX and execute it ***See note before clicking***<br /><br />https://community.dynamics.com/product/ax/axtechnical/b/mukeshhirwani_dynamicsax/archive/2012/09/19/delete-transactional-data-ax-2012.aspx<br /><br />***NOTE: this code WILL delete all your transactional data, use at your own risk. AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-20425997926306778782012-12-06T06:38:45.275-05:002012-12-06T06:38:45.275-05:00Hi,
Iam going to prepare production environment, f...Hi,<br />Iam going to prepare production environment, from test environment i have to delete all transactions and have to make Main Accounts values to zero. I am facing challenge making Main account values to zero, please guide me how to make Accounts value to zero. Even after deleting all the transactions and data still accounts are holding values. Please guide.D365F&O-Techiehttps://www.blogger.com/profile/18255288358019995091noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-56241872736521635772012-08-03T08:10:21.968-04:002012-08-03T08:10:21.968-04:00: ): )AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-45351489643309610172012-08-03T08:09:29.849-04:002012-08-03T08:09:29.849-04:00Thanks for sharing, Skaue. Yes, we would have that...Thanks for sharing, Skaue. Yes, we would have that problem on a big implementation, and that's why the model route is much safer in the long term.AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-62272831290924101652012-08-03T05:17:54.405-04:002012-08-03T05:17:54.405-04:00Another thing to consider is that XPO's do no ...Another thing to consider is that XPO's do no care about models. As far as I know, it is unaware of models. So you would have to keep track on what model you are exporting from in the source system, and make sure you import to the same model in the target system. For smaller customization it might be ok, but more complex XPOs could suffer from having changes from multiple models.tommy.skauehttps://www.blogger.com/profile/13189067870996112658noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-6852532519247562552012-07-31T09:55:25.460-04:002012-07-31T09:55:25.460-04:00Ok. You rock my world! Great summary, and yet anot...Ok. You rock my world! Great summary, and yet another great post on your blog. Keep it up! <br /><br />(yea, I mean it - it's not generic spam - lol)tommy.skauehttps://www.blogger.com/profile/13189067870996112658noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-16680628024858419762012-07-28T16:25:56.811-04:002012-07-28T16:25:56.811-04:00So based on what you are telling me. and assuming ...So based on what you are telling me. and assuming that you want to move stuff from Dev to Test as per your comment <br /><br />"As soon as you have used an xpo to transfer a table from one environment (DEV) to another (TEST), it seems impossible to update the TEST environment afterwards using a model store transfer."<br /><br />I would just restore the AXDB and the AXDevBaseline to Test. This should get rid of any conflict ID. The drawback, however, is that if you had any environment specific configurations, you will have to change them. <br /><br />Of course it depends on where you are in your Test env and if this change will impact deliverables. <br /><br />I hope this helps!AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-80796065312430670602012-07-28T16:13:53.922-04:002012-07-28T16:13:53.922-04:00At least one of them... ;-)
Still hoping to fix id...At least one of them... ;-)<br />Still hoping to fix id conflicts one way or another!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-79554808265499756962012-07-28T12:43:25.031-04:002012-07-28T12:43:25.031-04:00Hi,
Great question!
Then I would suggest conside...Hi,<br /><br />Great question!<br /><br />Then I would suggest considering restoring both the model and AXdb from the prod environment to the test one. It will work the same way as in 2009 when you would just take the application files (aod and ald files between environments along with the DB).<br /><br />I hope this answers your question.AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-70346050097633754962012-07-27T14:18:24.070-04:002012-07-27T14:18:24.070-04:00Very interesting post on how to prevent id discrep...Very interesting post on how to prevent id discrepancier! But others wondered too: how to resolve those discrepancies once you have got them?<br />As soon as you have used an xpo to transfer a table from one environment (DEV) to another (TEST), it seems impossible to update the TEST environment afterwards using a model store transfer.<br /><br />I had to use the -idconflict "overwrite" parameter, but as a result I could not synchronize some tables anymore. After altering some things in SQLDictionary I managed to synchronize again, but I lost all the data in the newly created table fields.<br /><br />No real harm done since it was only in the TEST environment, but I wonder if there is a way to correct id conflicts?<br /><br />As I see it now, we are supposed to transfer functionalities with xpo's from DEV to TEST and to a seperate "staging" environment where we collect all stuff that needs to be transfered to LIVE. From staging we can then use a model store move to LIVE. But what if the customer wants a copy of the LIVE on his TEST environment?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-41609990322929382952012-07-26T12:55:19.969-04:002012-07-26T12:55:19.969-04:00Thanks for replied. I understand your point here a...Thanks for replied. I understand your point here and that is what I have recommended to my client but it always take great effort to do refresh dev or test environments exercises. What i expecting was simple tool or program to rename some of the existing id values and make everything synchronize as it suppose.to be...S.C.GANhttps://www.blogger.com/profile/13760378056674583997noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-91342829796519730192012-07-25T19:47:56.978-04:002012-07-25T19:47:56.978-04:00Thanks!Thanks!AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-23667764057568111632012-07-24T17:22:15.960-04:002012-07-24T17:22:15.960-04:00Thankfulness to my father who informed me on the t...Thankfulness to my father who informed me on the topic <br />of this website, this webpage is in fact remarkable.<br /><i>Feel free to visit my weblog</i> - <b><a href="http://www.casino-gold.net/book-of-ra-online" rel="nofollow">nur</a></b>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-1732670217906346562012-07-23T08:43:46.780-04:002012-07-23T08:43:46.780-04:00Hi Rob, Microsoft does not have an argument agains...Hi Rob, Microsoft does not have an argument against xpo deployments. I think you said it right, you can still maintain ID values when moving modifications through XPO. However, and this is my personal opinion, xpos bring many challenges when moving modifications. One of them is moving labels files, the other is moving many different versions of many objects at once. I'm sure that you have experienced these at least once :D<br /><br />Anyway, Microsoft recommends moving the model store file as this guarantees you a successful deployment. As for your problem, do you have a deployment schedule? Perhaps by having a deployment schedule you can group your customizations into one model store file per week, instead of doing itmany times a day/week.AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-79493159649212229102012-07-23T07:03:02.927-04:002012-07-23T07:03:02.927-04:00I know that Microsoft says it's best practices...I know that Microsoft says it's best practices to move models, but it you have multiple smaller customizations (e.g. reports) that are in development and you need to move these frequently from DEV to TEST, then this becomes quite the operation. You can still preserve object IDs by using XPO's. Do you know what Microsoft's argument is against using XPO's ?Robhttp://www.vanbran.comnoreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-33015646102653528412012-07-22T23:31:16.903-04:002012-07-22T23:31:16.903-04:00Hi! ... hey thanks for reading my blog and I'm...Hi! ... hey thanks for reading my blog and I'm glad that you found this article interesting. If you don't mind the question, What kind of discrepancies are you experiencing? Is it metadata? This is one of the biggest issues that I'm hearing in the past few months and it is a problem as if you have a running AX 2012 instance running and your stage and test are different, then you should make them as per production specs (at least from a model store point of view)<br /><br />It would be great if you could share what kind of issues you are experiencing right now.AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-34543557631142460392012-07-22T03:48:49.743-04:002012-07-22T03:48:49.743-04:00Great post!
Now I am more concerns about how to r...Great post! <br />Now I am more concerns about how to resolve if you have id discrepancy in both environments? To minimize the impact of production system.S.C.GANhttps://www.blogger.com/profile/13760378056674583997noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-82979780587114940402012-07-20T13:23:26.058-04:002012-07-20T13:23:26.058-04:00Thanks!Thanks!AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-40534988270901796742012-07-20T12:29:33.020-04:002012-07-20T12:29:33.020-04:00Great summary!Great summary!Anonymousnoreply@blogger.com