December, 2009

  • Microsoft Dynamics NAV Team Blog

    Overviews of Released Platform Hotfixes for Microsoft Dynamics NAV 5.0 SP1, Microsoft Dynamics NAV 2009, and Microsoft Dynamics NAV 2009 SP1

    • 1 Comments


    Overviews of released platform hotfixes for Microsoft Dynamics NAV 5.0 SP1, Microsoft Dynamics NAV 2009, and Microsoft Dynamics NAV 2009 SP1 are available on PartnerSource and CustomerSource at the following links:

    PartnerSource:

    Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 5.0 SP1

    Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2009

    Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2009 SP1

    CustomerSource:

    Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 5.0 SP1

    Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2009

    Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2009 SP1

  • Microsoft Dynamics NAV Team Blog

    Update to Microsoft Dynamics NAV 2009 Developer and IT Pro Help

    • 0 Comments

    We've released an update of the Microsoft Dynamics NAV 2009 Developer and IT Pro Help to MSDN and the Microsoft Download Center. This release includes new and updated content in the following areas:

    • Automation
      • Added new topics and updated existing topics about using Automation with the RoleTailored client.
      • Improved Automation walkthroughs
    • Arranging Page Fields in Rows and Columns
      • Added topics about how to use the FixedLayout control to arrange page fields in rows and columns.
    • Multilanguage Functionality
      •  Updated the topics about developing multilanguage-enabled applications and installing language modules.
    • FIND and FINDSET functions
      • Added information about when to use the FIND function and when to use the FINDSET function.
    • Code Rules in Form Transformation
      • Updated existing topic to fix examples and improve clarity.
    • Redesigning Matrix Forms for Form Transformation
      • Updated topics to reflect the new redesigned matrix forms in Microsoft Dynamics NAV 2009 SP1.
      • Added a new walkthrough with details about how to redesign a matrix form.
    • Web Services
      • Added numerous clarifications and enhancements, including a new Web Services Programming Tips topic
    • Best Practices Analyzer for Microsoft Dynamics NAV 2009
      • Added references in two topics for this new diagnostic tool, which identifies configuration issues that might be preventing your three-tier deployment of Microsoft Dynamics NAV from working correctly and is available separately as a download.
    • Configuring Access Control Lists with Microsoft Dynamics NAV 2009 Web Services
      • Added information to clarify best practices when configuring Web services to use SSL, configuring Web services to use delegation, or configuring Web services to use both SSL and delegation.

    Some of these updates are based on feedback that we received from the community. We love hearing from you about how we can make the Help even better! We encourage you to continue to use the feedback link at the bottom of each page in the CHM, or use the Ratings and Feedback form on each MSDN page to tell us what you think.

     - Bob, Jill and John (the writers for NAV Developer and IT pro Help)

  • Microsoft Dynamics NAV Team Blog

    Transformation Tool : FontBold on Controls

    • 5 Comments

    FontBold property sets a value that indicates whether to display text in boldface. This property applies to form controls. In standard application this property is normally used to display accounts that are not posting accounts in boldface (form16 - Chart of Accounts). 

    For a page field control, Style Property is used to format the text that displays in a page field. More details about this can be found in Microsoft Dynamics NAV Developer and IT Pro Documentation, designing pages.

    When running Transofrmation Tool to transform forms to pages in NAV 2009 SP1, records displayed in boldface on a form are not displayed in boldface on the page, after the transformation.

    To change this, following files should be modified:

    Page.xsd (add property definition to page field control):

          ....

          <xs:element name="ClosingDates" type="NavBoolType" minOccurs="0" maxOccurs="1" />
          <xs:element name="Numeric" type="NavBoolType" minOccurs="0" maxOccurs="1" />
          <xs:element name="DateFormula" type="NavBoolType" minOccurs="0" maxOccurs="1" />
          <xs:element name="Style" minOccurs="0" maxOccurs="1">  <!--  This is where the Style property is added. BEGIN changes  !-->
          <xs:simpleType>
              <xs:restriction base="xs:string">
                  <xs:enumeration value="None" />
                  <xs:enumeration value="Strong" />
                  <xs:enumeration value="Attention" />
                  <xs:enumeration value="Favorable" />
                  <xs:enumeration value="Unfavorable" />
              </xs:restriction>
          </xs:simpleType>
       </xs:element>
       <xs:element name="StyleExpr" type="xs:string" minOccurs="0" maxOccurs="1" />   <!--  This is where the StyleExpr property is added. END changes  !-->
    </xs:all>
    </xs:complexType>
    ....

    Now that we have added Style and StyleExpr properties to the field control in page definition, we must modify CodeRules.txt file to transfer UPDATEFONTBOLD function to <FieldName>Emphasize variable defined for each field on page (that UPDATEFONTBOLD function was called for on a form).

    In addition, Style property of the field shuld be set to Strong, and StyleExpr property to <FieldName>Emphasize. Transformation tool already creates a trigger called <FieldName>OnFormat for each field affected, that sets the value of <FieldName>Emphasize variable conditionally.

    In short, replace the following code in file CodeRules.txt:

    .....

     <find>
    !currForm!.!var1!.UPDATEFONTBOLD :=
    <declareVariable>
    !var1!Emphasize
    <declareVariableType>
    Boolean INDATASET
    <replace>
    !declaredVariable! :=
    <comment>

    .....

    with

    <find>
    !currForm!.!var1!.UPDATEFONTBOLD :=
    <replace>
    !currForm!.!var1!.UPDATEFONTBOLD :=
    <moveValueToProperty>
    Strong
    <movePropertyToControlName>
    !var1!
    <moveToProperty>
    Style

    <find>
    !currForm!.!var1!.UPDATEFONTBOLD :=
    <declareVariable>
    !var1!Emphasize
    <declareVariableType>
    Boolean INDATASET
    <replace>
    !declaredVariable! :=
    <moveValueToProperty>
    !declaredVariable!
    <movePropertyToControlName>
    !var1!
    <moveToProperty>
    StyleExpr

    Run transformation tool on from 16, import and compile the page. When running page 16 (Chart of Accounts) the records should be displayed in boldface, the same way they are displayed on the form.

    Jasminka Vukovic 

    Microsoft Dynamics NO

    Microsoft Customer Service and Support (CSS) EMEA

    These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

     

     

  • Microsoft Dynamics NAV Team Blog

    Calculated field on a page is only recalculated when the OnValidation trigger is run

    • 0 Comments

    Summary

    If you have a page field that has a calculation as its SourceExpression and part of the calculation depends on another field, then the calculated field is not automatically recalculated when the other field is updated. The calculated field will first recalculate when the updated field's OnValidate trigger is run, which  only runs if it contains code. So to enable the calculated field to recalculate automatically, you must put some code on the OnValidate trigger of the field that gets updated - even if it is only a comment line with no functionality.

    Note: A page will only update a field if it detects that there is some code on the OnValidate trigger. This is done for performance reasons to avoid unnecessary updates.

    Example

    Let's say you have the following two fields on a page:

    Field1:
    Name=Txt1;
    SourceExpr=Txt1;

    Field2:
    Name=NewTxt1;
    SourceExpr=Txt1 + 'XYZ'

    Field2 is supposed to add the text 'XYZ' to the value is entered in Field1. But when you enter a value in Field1, Field2 does NOT get automatically updated. To change this behaviour, add some C/AL code to the OnValidate trigger of Field1. For example, just add a simple comment like "//" or:

    //This comment is used to update Field1 - do not delete

    This will tell Field1 to run the OnValidation trigger, which in turn updates the other fields on the page.

  • Microsoft Dynamics NAV Team Blog

    How would I use RIM and Style Sheet Tool to handle change of Tax Number (OiB) in Croatia (Part 2 of 3)

    • 0 Comments

    In my previous post, I described the problem of the tax numbers in Croatia being changed. In this post, I will describe the first steps to solve the problem. In part 3, I will describe what to do when you receive the new tax numbers. The business process from customer perspective looks like this:

    1. Export customer, vendor and contact data from Dynamics NAV to Excel file
    2. Request customers, vendors and contacts for their new tax number using documents created with help of Style Sheet Tool
    3. Enjoy the year end holidays with friends and family
    4. Update data exported in step 1 with new tax number received from customers, vendors and contacts and import it back in Dynamics NAV

    Export data from Dynamics NAV

    Here is the overview of how I did this in NAV HR 5.0 SP1 Feature Pack 1:

    1. Click Application Setup-> Company Setup-> Data Migration in Administration application domain to open Migration overview form.

    ivan1

    2. Create 3 lines by entering table IDs of Customer, Vendor and Contact tables (and any customized tables you might have that contain VAT Registration No.).

    3. Position cursor on line representing Customer and click Migration-> Migration fields menu item to open Customer - Migration Fields form.

    ivan2

    4. Place a checkmark in Include field for each Customer field you want export. At minimum (to complete this task place checkmark in Include field of lines representing following fields:

    • Name - this will allow you to see see which customer's VAT Registration No you're changing
    • Country/Region Code - this will allow you to filter out only Croatian customers (having Country/Region Code set to HR or empty)
    • VAT Registration No. - this will allow you to see the "old" VAT Registration No.

    Optionally, if you decide to use exported data for Mail Merge this data and send to customers, vendors and contacts to ask them for their new tax number, you may need to include following information as well:

    • Address - this will allow you to send the documents by mail
    • Address 2 - this will allow you to send the documents by mail
    • Post Code - this will allow you to send the documents by mail
    • City - this will allow you to send the documents by mail
    • Fax - this will allow you to send the documents by fax
    • E-mail - this will allow you to send the documents by e-mail

    5. When satisfied click OK to return to Migration Overview form.

    6. Repeat steps 3-5 for Vendor and Contact tables and when satisfied click Functions-> Export to Excel on Migration Overview form to export data to Excel.

    7. When asked, select folder and file name in which to store exported data and click Save.

    8. System will export data and notify you when it's done. The result should be excel file with 3 worksheets (Contact, Vendor and Customer) containing data from selected fields.

    ivan3

    NOTE: Depending on which method you’ll use to collect data from customer, vendors and contacts you’ll need various degrees of data detail from Dynamics NAV.

    Request new tax number from customers, vendors and contact

    For the sake of example, I'll assume you'll request your customers, vendors and contacts to send you their new tax number using regular mail (as it should be the hardest to setup), using data exported from Dynamics NAV created in previous step.

    NOTE: I assume you successfully imported Style Sheet Tool objects 1.1. as described in User Guide for Style Sheet Tool.

    Here is the overview of how I did this in NAV HR 5.0 SP1 Feature Pack 1:

    1. Open Object Designer and run Form 680

    ivan4

    2. In the Code field, provide a code for naming the style sheet you are about to create. This could be, for example, CUSTOMER_NTN.

    3. In the Description field, type in a description of the style sheet, for example, Request Customers New Tax Number.

    4. In the Form No. field, click the Lookup button and in the Style Sheet Object List window, select the Customer List form (form 22).

    5. In the Table No. field, click the Lookup button and in the Style Sheet Object List window, select the Customer table that is associated with Customer List. In this case it is table 18.

    ivan5

    6. In the Base Record field, select the Base Record check box.

    7. In the Multiple Lines field, select the Multiple Lines check box.

    8. Click Style Sheet, Select Fields to open the Customer - Style Sheet Fields Used List window. These fields are the ones you want to show in the final, merged Word document.

    9. In the Field No. field, click the Lookup button, and in the Style Sheet Field List window, select, for example, the fields Name, Name 2, Address and other. The Include Caption check box in the Item - Style Sheet Fields Used List window has automatically been selected for each field. This will make the caption of the fields available in your Word document. If you do not want captions but only want the data fields to be visible on your document, clear the check box for the field captions you do not want.

    ivan6

    10. Close the Item - Style Sheet Fields Used List window.

    The fields to use for Customer have now been defined and you are ready to merge the selected fields into a Word document as mail merge fields.

    11. On the style sheet card that you just created, click Style Sheet, Create Mail Merge. This will open up Word. The fields you have chosen for the Customer will now be available in Word.

    12. In Word, click the Mailings tab, Insert Merge Field and select each field one at a time. Design the document as necessary by adding your own text and pictures. The mail merge could look like this:

    ivan7

    NOTE: Make sure to insert a table element between MULTILINE_BEGIN_Customer  and MULTILINE_END_Customer merge fields. This will ensure text within table element to be repeated multiple times.

    13. Close Word when you are finished.

    You will now return to Microsoft Dynamics NAV.

    1. Click Yes to import the mail merge document.

    2. Click Yes to convert the mail merge document to a style sheet document.

    3. Click Yes to update Manage Style Sheets. This will associate the style sheet you just created with the Customer List.

    4. In Microsoft Dynamics NAV, on the main menu, click Financial Management, Receivables, Customers to open the Customer Card.

    5. Click Customer, List to open Customer List

    ivan8 

    6. Filter the list by Country/Region code selecting customers you want to prepare to documents using Style sheet you created in previous steps

    ivan9

    7. On the Toolbar, click Send Options.

    ivan10

    8. In the Send Style Sheet Card to Microsoft Word - Program Selection window, select Microsoft Word and click Send

    A Word document will be generated based on the Customer style sheet you have just created, and filtered data from the Customer List is imported to a Word document which now looks like this:

    ivan11

    You can do the similar thing with vendor and contact records.

    To reuse the settings and documents used in this example follow these steps:

    1. Open Object Designer and run Form 680.

    2. Click Style Sheet, Manage, Definition, Import to import style sheet definition.

    3. Select example.xml file attached to this document (within example.zip file).

    4. Click Yes to import the mail merge document.

    5. Select example.docx file attached to this document (within example.zip file).

    6. Click Yes to convert the mail merge document to a style sheet document.

    7. Click Yes to update Manage Style Sheets. This will associate the style sheet you just created with the Customer List.

    Enjoy year end holidays with family and friends

    I'll leave you to decide the way you handle this part! :-)

    -Ivan Koletic

  • Microsoft Dynamics NAV Team Blog

    Treemap Business Data Visualization available on PartnerSource

    • 1 Comments

    The “Treemap Business Data Visualization for Microsoft Dynamics NAV 2009 SP1 – Partner Community Edition” is available for download on PartnerSource. It will be available on CustomerSource in a few days.

    For more information about using this add-in, take a look at Christian's blog.

  • Microsoft Dynamics NAV Team Blog

    Dynamics NAV RTC hangs when previewing/printing reports

    • 0 Comments

    Problem:
    When previewing a report you only getting a small window in upper left corner with only a text string with the name for the report and the rest blank. When I trying to close this window, you get an error message: "Errors exist. Do you want to discard changes?" (Y/N). Pressing Yes, hangs and close the RTC client.

    Probably cause:
    You have installed the RTC client outside the setup chainer or you have uninstalled Report Viewer 2008. It may also be that Report Viewer 2008 installation is broken.

    Solution:
    Run DVD\Prerequisite Components\Microsoft Report Viewer 2008\ ReportViewer2008.exe and select install or repair depending on if Report Viewer 2008 was already installed.

Page 1 of 1 (7 items)