If you are able to always have a stabilised layer its very nice to use the way the consultant talks about. Because you are then 100 % sure that you are operating with the same table ids and so on in both enviroments.
If it's hard to keep the dev enviroment stabilised at all times, the export/import solution is just super!
It's also nice with the export/import rutine that you can do it when people are one the solution, not always, but most of the times.
Best regards Jacob
At 13:00 22.01.2004 +0000, you wrote:
Hy,
When we began with axapta programming, one of our consultant said
that the usage of Import/Export project was a wrong solution.
Then, he adviced us to import our developpement by making a copy of
the "CUS Layer". But, in this case, before each copy, we need a
stabilised layer. And, some people have to wait others before
beginning a new developpement.
Then, what's the best solution for developpement importing in the
Live environment??
What do you use??
Thanks a lot
Thierry
Yahoo! Groups Links
- To visit your group on the web, go to:
- http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
- [EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
