One thing I'm looing forward to, an I hope it is the case is the customization done by US to all the forms is lowered. I've been merging an addon from W1 version to US and Comparing forms in text comparing tools mind numing. The main reason why US modifies these forms is because of zip and state text boxes . They change some other fields as well based on US companies work. I think they should leave them the same way, It's just extra maintainbility that is not needed. Anyways coming to my point. With V.5 hopefully they don't have to do this. because Pages get rendered based on importance, so all they have to do is make some fields more important than others, and US locations are not needed.
[-o<
Ahmed Rashed Amini
Independent Consultant/Developer
blog:
https://dynamicsuser.net/nav/b/ara3n0
Comments
I had to change the values to default to import it back to navision.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
The Caption for Multi language shouldn't be part of a property but a table. Having 4 captions and comparing a world wide to US, for text comparison is horrible.
Also why Does US change (LCY) to ($) in every object. Is this realy needed?
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
RIS Plus, LLC
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I believe you will still have ($) instead of (LCY) in ENU version. Also you have now a modified objects that for upgrade purposes will be another mess.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I wish that you could merge the tables, but don't compile it so that during import it doesn't error out. Do this only when you are merging te table objects. after you've imported the objects. You can compile the objects.
[-o<
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I think the only thing needed is writing appropriate upgrade docs for add-ons and customer developments and then everything is OK.
For example, I had a custom development for confirming vendor invoices, with 2 confirming users, each having a noneditable textbox and a button in a container on the form... and I just wrote "copy-paste container called Confirmation" in the Documentation trigger, and then later on it was really easy to copy-paste it...
One thing that developer should follow is make their variables local so that when you copy functions it copies those variable as well.
We still cannot search for fields when we design the table.
A trick that I've found out for this. You select the field in table designer then you click the grey area to make the record noeeditable. Then you hit the first letter of the field. This will find the first field. Then you select the record again and hit the first letter. One you've passed the first page of fields, you just keep hitting the first letter.
I think I should put this on tips and tricks section.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
When I know I need to do some work in a table, I copy/paste into Excel. Finding the name in Excel is much easier. Then when I get the ID of the field I need, I go back to Table Designer and can look it up by the ID.
I attempted to use the method you described but cannot figure out what you are referring to. Could you please provide a bit more detail?
Microsoft Dynamics NAV Developer
In object designer. click on table select item table and click design. The cursor will be on "field No.". Hit TAB to move to the next field "Field Name". Now select the record by using the mouse and clicking the left gray column (it has the black triangle).
Once the record is selected, you'll notice that the whole record is blue, and that "No." field name becomes uneditable. Hit the letter C and the cursor will move to Class field.
One more thing. I tested this in SP2 with improvement and it looks like it doesn't work on that version. But it works all the way to SP1.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Ta!
Kris
Microsoft Dynamics NAV Developer
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Microsoft Dynamics NAV Developer
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
But, it stays that in some circumstances, that feature can be unavailible... :roll:
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
will do.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Your "feature" for finding fields by typing name, ofcourse
I meant, that it is possible to mess up the zup file (or whatever else) and cause of that to not to be able to use that feature.
Oh, nevermind
Fortunately it was in the Navision training 8 years ago and I use it every day without thinking. :oops:
Sorry I never mentioned it.
As for you not sharing, that's ok. We'll get out the wet noodle and call it even. *sly grin*
Microsoft Dynamics NAV Developer
This trick is almost the biggest improvement in the C/Side GUI since, well, ever..?? ](*,)
Fighting for 1st place with the ability to scan through functions by their first letter introduced in 3.70. Damn the C/Side GUI is a pity #-o
Peter
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
a bit annoying, but still better than scrollign through the list.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Sometimes it does not work though :evil: but it is definatelly better then was before!
Oleg