Hello Folks, I am a little bit confused. Attain … Navision ?! Means this that i can Navision 2.6 upgrade to Navision Attain, or is Attain a completly new solution? ------------------ Best regards Alejandro Schubert CYCOS AG System Engineer www.Cycos.com www.Dolphinct.de EMail: Alejandro.Schubert@Cycos.com
Yes, Navision Financials 2.60 can be upgraded to Navision Attain. Navision Attain = Navision Financials + Advanced Distribution + Manufacturing On top of that Attain offer new modules like : - Service Management - Capacity Requirement Planning - Relationship Mangement (used to be called Contact Management in Finacials) So in essence, unlike NF 2.60, Navision Attain 3.0 is a major release in terms of new features, modules, functionalities …###### _________________________________ Tarek Demiati Freelance Navision Developer Email : email@example.com Telephone : +65 - 906 787 16 _________________________________Edited by - Tarek Demiati on 2001 Sep 07 15:14:28
… + new C/SIDE features.
we are going to upgrade our system from DE2.50 to attain 3.01. What are your experiences regarding the mentioned release ? Any problems known ? Which new features offers C/SIDE ? Is there any incompatibility know with older versions like our DE2.50 ? i would appreciate to get some of your impressions concerning attain. Stefan Weinreich Billing Analyst
Hello, there seem to be a lot of problems with Attain at least in ther german version. After weeks of trouble (performance) we decided to downgrade to 2.60. Another german company experienced more or less the same problems some weeks later. I think it should be better to wait a couple of months until Navision is willing and/or able to realize that Attain 3.01d is not to be used in installations > 50 users.
Wolfgang, to what do you attribute the reduced performance you experienced in Attain? Dave Studebaker firstname.lastname@example.org Liberty Grove Software A Navision Services Partner
I’d like to know about any new C/Side features. Also, be aware that a good part of Advanced Distribution was not put into Attain and some parts may never be. WMS, Warehouse Documents, Bins, Contract Pricing, Usage-based procurement, and RF devices. David Rochford Zesco Products 317-269-9300 x188 email@example.com
Right now, I’m in the middle of an upgrade of Navision 2.60b Mfg to Navision Attain 301A (Us version). I looked at the steps to take. It doesnt seems to be that hard. The only thing I get is that weird ‘Navision Developers Toolkit’. I’m getting all the time errors in my object text file output after I did a merge. Anyone has any experience with that? Roelof.
what king of problem does navision attain has with more than 50 users? and what kind of new c/side features? are you referring to the dynamic naming of the field names, like how navision have used it for naming its dimension fields?
Originally posted by daves: Wolfgang, to what do you attribute the reduced performance you experienced in Attain? Dave Studebaker firstname.lastname@example.org Liberty Grove Software A Navision Services Partner
I’m sure that Attain is working very well in Micky-Mouse-installations. As soon as high performance is needed there is a major bottleneck which is caused by the SQL-statements which are sent to the SQL-Server. Even after doing a lot of fine-tuning on the SQL-server the response time is inacceptable. As far as I know there are only few (two)installations > 100 clients and both ended up in a desaster for the companies (both lost more than 1 Mio USD in the end due to the malfunctions). One is ours and we decided to re-migrate to C/SIDE. Navision was unable and not really willing too help, the NSCs were more or less completely helpless and practised actionism. In our case a Microsoft SQL-specialist checked the system in order to detect problems in the middleware; nothing changed. There are too many fundamental differences between C/AL and SQL in the way of programming , for example the use of filters, the way of locking tables or records. That means in the end that either the C/AL-code has either to be completely changed to be copatible with the way an SQL-DB is working or the SQL-translator has to be optimized to produce a certain compatability(which is hardly possible in my eyes). The logic and the handling of the to DBMS are too different in the end. Regards, Wolfgang
that would conclude that navision attain does not run as well as how navision financials is running in sql environment?
Navision Attain 3.01B SQL has much improved performance than 2.6 for a 2.6 application (i.e. for the same application as you are running in 2.6). An Attain application is more complex and introduces several levels of indirection with the dimmension tables. The result is many more server calls. However, much work has been done between 3.0 and 3.01B for performance, so it is a question of benchmarking the differences.
The new C/SIDE features (development environment and database) can be found in the changes document for 3.01.
Do any of you SQL experienced folks have suggestions (tips and tricks) on tuning Navision for SQL? I am of the opinion that SQL is significantly slower than the Navision native database in almost all cases. But I am hoping some of you may know, and be willing to share, ways that one can tweak Navision to make it run better in the SQL environment. At least pointers on what not to do in modifications. Thanks in advance for any help. Dave Studebaker email@example.com Liberty Grove Software A Navision Services Partner
Morning, We are currently using Navision version 2.6E on SQL 2000 and are experiencing poor performance, despite having a greatly overspec’ed hardware. We have a 12 Gb database and approximately 60 users. Navision UK and our NSC have advised us to upgrade to Attain 3.01b, which we are looking to do next week. However, having seen a couple of the posts here saying that in fact 2.6E is faster, I’d be interested to hear other opinions. Thanks Justin Tucker Navision Support/Analyst Home Entertainment Corporation
David Rochford said: I’d like to know about any new C/Side features. Also, be aware that a good part of Advanced Distribution was not put into Attain and some parts may never be. WMS, Warehouse Documents, Bins, Contract Pricing, Usage-based procurement, and RF devices. ++++++ Are these features going to be missing completely, or are they being (what I like to call) metomorphisized into Attain? An example of what I call metomorphisizing of Distribution would be the Returns Management area in NAD 2.60. The functionality is all there (and greatly improved upon, in my opinion) in Attain, but functionaly is VERY different from the NAD version. ++++++ Roelof de Jong said: Right now, I’m in the middle of an upgrade of Navision 2.60b Mfg to Navision Attain 301A (Us version). I looked at the steps to take. It doesnt seems to be that hard. The only thing I get is that weird ‘Navision Developers Toolkit’. I’m getting all the time errors in my object text file output after I did a merge. Anyone has any experience with that? ++++++ I have experienced this problem, Roelof. I examined the text output file for one of the “import errors”, and could not see the problem (I had an extra “}” according to the Attain import). I’m in the process of re-comparing this “merge” file with the 3.01.b base export file using a third party text comparison tool called ExamDiff Pro. It has proved a very effective tool for us on some other implementations. My hopes are that the recompare will show the errors and I can clean up the merge file. Regards, all! Kristopher Webb Kelar Corporation, Canada
FYI: I just got the Attain 3.01B update for the US yesterday. The update contained 218 objects. David Rochford Zesco Products 317-269-9300 x188 firstname.lastname@example.org