Skip to main content
Submitted by Suzanne Scanlan on 20 March 2020

ArcherPoint Dynamics NAV / Business Central Developer Digest - Vol 285

ArcherPoint Dynamics NAV and BC Developer Digest Blog

The Dynamics NAV and Business Central community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of  sharing helpful information with one another to help customers be more successful.

As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV/BC experts and devotees around the world. We hope these insights will benefit you, too.

Microsoft Dynamics 365 Business Central 16 Table List

Here’s one for your bookmarks: Erik Hougaard posted All the ‘2 Billion’ Tables in Business Central 16. 

Using Bank Import in Business Central: An Important Process for Proper Functioning

Ryan says: “Something I learned yesterday that might be helpful to everyone here. At a client, we're using the Bank Import functionality in BC to import text files for the Bank Reconciliation table. Pretty standard stuff; however, we learned that, instead of sending negative amounts to denote debits (for the bank), they are sending a conditional value in another column: D for debit or a C for credit.  

To allow this to process correctly, you'll need to map the conditional value column to the same field as the Statement Amount (in the first screenshot) and then on the Column Definitions, then type in the Negative-Sign Identifier (second screenshot). So now, BC/NAV will make the statement amount negative when it comes across a “D” on the same line:


Figure 1 – Field Mapping in Microsoft Dynamics Business Central: Statement Amounts


Figure 2 – Type Negative Sign Identifier in the Microsoft Dynamics Business Central “D” or “C” Field

 

Here's the kicker: The bank sends both a “D” or “DR” to denote a debit. Unfortunately, the Negative-Sign Identifier can only work with the entire value (i.e., you cannot use a filter like D|DR). Luckily, it sends a C for credit (and not a CR). Here's what I did:

In the Field Mapping, there's a hidden column called Multiplier you'll need to show. The default value in this field is 1.00. For the Statement Amount column, I changed the multiplier from 1.00 to -1.00. This will bring in all amounts as a negative. 

And then for the Conditional Value column, I changed the Negative-Sign Identifier to a C, which it then multiplies it by -1, giving us a positive amount.

There's not a lot of documentation on utilizing the Bank Import and Data Exchange definitions, but I hope this helps.

Crystal asks for clarification: “Thank you, Ryan. Is this import process for a specific bank, or is it a generic import for all banks?"

Ryan replies: “This can be used for all bank statement imports, regardless of bank.” 

Alan: “Ryan, this was a great find. Thanks.” 

Physical Inventories in Business Central

Roberto Steffanetti shares some interesting functionality in Business Central that allows for inventory counts to be subdivided. Check out his post: Physical Inventory Orders in Business Central.

 

If you are interested in Dynamics NAV and Business Central development, be sure to see our collection of NAV/BC Development Blogs.

Read the "How To" blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.

Blog tags