Back to Blog
Buffer wordpresscom integrations7/5/2023 ![]() Click on the History button at the ribbon.Dimensions Connector as the Connector Name. To achieve this we have to enable the “Use a Temporary Table” checkbox of the DimensionBuffer table of the Internal Document. ![]() We actually don’t want these records to be inserted into the physical table. The records are now imported in the buffer table.Open the BG Dimension Buffer table from the Object Designer: Setup the mapping between external and internal documents.Create a new Connectivity Studio Connection with the following building blocks: FILEREADER, MAPPER and RECORDGENERATOR.Create the Internal Document for the Purchase Header, Line and the BG01 Dimension Buffer tables.Create an External Document for the sample Xml document (tip: use the function “Create From Sample” of the External Document card page).Create the following Custom Connector (please checkout the BIS2013 SDK which is included in the standard installation package).In addition we have to use a custom table which is used as the interface on the standard Dimension system. We cannot use the standard Dimension Set table to import the values.Each purchase line has one or more dimensions. Scenario: Import a Purchase Order with Lines. This scenario will be demonstrated in this blog post. The standard system is sufficient for all tables except the dimensions. Using a Custom Connector might be a better choice.In this case an XmlPort might not be the best option since sales and purchase documents tend to be changed regularly. Always try to find the right balance between a complex configuration vs simple customization. That might be a good solution in complex scenarios. By doing this you need to handle the complete import in the XmlPort. It is always possible to use an XmlPort Record Generator in your pipeline. An XmlPort is usually the fallback scenario. Use an XmlPort and solve it with customization.We need to run the magic code which is under the Dimensions button at the user interface. As said it is not possible to import the dimensions directly. The concept of BIS is that it uses Documents to import data into Tables. ![]() The Dimension Set ID is assigned to the source record and there you go.Īs you see there is happening much more under the hood than you would expect. This might result in a new Dimension Set ID. If you close the Dimension table it will check if there are any changes and process them to the actual tables. The Dimension page is based on this temporary table. If you click on the Dimensions button in NAV2013 it will load the Dimension Set Entries of the current document into a temporary table. What happens if you create a purchase order with dimensions manually? Although the user experience looks quite similar to NAV2009 the implementation is completely different. In this blog article I would like to demonstrate how to import a purchase order with dimensions with BIS2013.įirst of all lets apply golden integration rule: if you cannot do it manually you cannot automate it. You always need to run some code to create dimensions. ![]() ![]() As a result it is no longer possible to import dimensions into the Dimension tables directly. The source records only have a reference to a collection. Instead of creating new records for each document / dimension code combination it assigns a unique id to a collection of dimension code / value combinations. The 2013 dimension concept tries to reuse Dimension Combinations as much as possible. This has an direct impact on integrations which import dimensions into Microsoft Dynamics NAV. One of the major changes of Microsoft Dynamics NAV2013 compared to NAV2009 is the dimension system. ![]()
0 Comments
Read More
Leave a Reply. |