Entchen & Geepz Blog

Habe schnell eine neue Webseite erstellt Irgendwann (wenn's Zeit erlaubt) wird auch diese Blog dorthin übertragen. Bis dann

Geepz Business Servicess GmbH

This property changes dramaticly way Navision sorts the code fields...

Using SQL Server option for Navision? "Sometimes" you have performance problems, haven't you?   It could be helpful to create some SQL VIEW, associate it with a Navision Table and make it visible through Navision...

Wozu wir es brauchen können ist ziemlich klar, denke ich. Firmenmitarbeiter sind oft unterwegs, unglückliche weise auch meistens offline oder ohne VPN- oder Terminal Server Zugriff auf Firmen Navision Datenbank. Dazu haben die einmal Microsoft Outlook, einmal Lotus Notes, The Bat, Mozilla oder sind sie sogar mit einem Apple unterwegs. Alle diese Adressbuch-Software unterstützen den vCard-Format um Kontakte zu importieren. Und was noch positiv ist - vCard kann eine Kontaktkarte wie auch mehrere beinhalten. So kann man die ganze Navision Adressendatenbank in eine einzelne Datei exportieren und in beliebiger Software wieder in einem Schritt importieren.

Why should we do this is clear, I think. If you need your Navision Contact for Microsoft Outlook, Lotus Notes etc., this is the simpliest way to prepare the right form for such applications. Important thing - vCard can contain either single or multiple contact instances. So we are able to make a single vCard file containing all our contacts.

The task becomes challenging first when we?d like to show temporary data on forms, not only use them hidden within our code. Yes, there is a new powerful property available starting with NAV 5.00 version which fully satisfies our needs. However, not every customer is about to make a decision to upgrade his system to this version in a near future. (anyway, wild usage of this new property could be a bit dangerous, especially when developing in a team and using DELETEALL commands So let's have a look at some tricky workaround steps allowing us to implement similar functionality not having to upgrade the system.

Temporäre Tabellen in Navision sind allen gut bekannt. Das Man diese aber mit ein Paar Tricks auch als SourceTable eines Navision SubForms gut und einfach verwenden kann muss nicht jedem ganz klar sein. Da habe ich mich mal entschieden so ein Master-Detail Beispiel mit einer temporären Tabelle zu machen. Falls es also jemandem interessierte, bitte hier lesen.

Have you got such customers, too?  Always talking about Gray Levels, LightGreen2, DimGrey, DodgerBlue, FireBrick, FloralWhite, ForestGreen , Fuchsia, etc., etc... To calculate them based on well known Navision RGB-formula all the time.. this could be a bit annoying and slower job...

Personally I don't like the way how CRM stores the country information. It is a plain text field, so users can enter what they like, use abbreviations or the full name of a country, spell it lowercase or uppercase. Creating good reports based on text fields is much more complex than comparing against integer values, so a picklist holding the country would be more appropriate in a CRM form.

(Source: Stunnware CRM Blog)

One of the questions asked over and over again is if it is possible to change the default view of a related entity. Let's take the history view in an account form. It defaults to the "Last 30 days":

(Source: Stunware CRM Blog Information)