Skip to main content

NAV - RTC personal view and experience

In my personal experience RTC has been great. Here are some positives and negatives from my experience.

Positives:
1) Personalization of the RTC - role centre/cues/fields etc. Everyone loves it.
2) Web Services - I used this in my first implementation. Easy to use/very stable/fast to implement. Best thing since sliced bread. :)
3) Reports - You can create some nice reports. Save to pdf and excel is a bonus.
4) Training and adoption - you will find that adoption will be great. I found my client basically really taking charge and personalizing the client to their needs and to their teams needs.

Negatives:
1) Batch processes - They are slower.
2) Large reports cause issues (may crashes in some incidents) - there has been some changes in SP1 but I don't think it fixes it totally. But it is a good improvement.
3) In a fast data entry environment. Where you have people just entering orders all day. RTC is actually slower for them. NAV classic has always been great with shortcuts. Maybe this just needs getting used to. They seem to be accepting/enjoying it more as time goes on.
4) Reports - they take a little longer to develope. After you learn the tools. This is not a negative any more.
5) Matrix forms - not so great in RTC. It is a lot easier to use the Classic client for analysis by dimensions and similar forms.

Transformation tool - I only use the executable to create the page. Then I manually keep the form and page in synch. I find this so much faster.
I personally will use the transformation tool if I had a repetitive task. Like maintaining an add-on.

Overall - the positives outweigh the negatives. Even though I am mentioning more negatives (its easier to complain than to praise).

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !set.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi