Data Import into Nav

(0) Share

Report

Posted on by Jag S

214

Hi All,

We are planning our Nav implementation with a Microsoft Partner and will be integrating NAV with our Housing system which has SQL backend. The customer payments will be entered in the Housing system which will be imported into NAV. It was surprising the NAV Partner mentioned that we should not import customer level transactions into NAV. He said the payments will be imported against the property dimension, instead of customer dimension. In the Housing system customer transaction table the payment is against both customer and property.

I asked the MS partner why we should not bring transactions based on customer_id and he said that it will be a lot of data and we should not create a dimension for customers.

I'm confused why we should not create a customer dimension as the transactions will be same whether its customer based or property. Also what in the future finance wants to create customer based reports.

Please advise whats the best approach as I understand NAV is a robust system and can handle a lot of transactions.

Thanks

Jag

*This post is locked for comments

I have the same question (0)

All responses (15)

Answers (0)

Suggested answer

Tharanga Chandrasekara 23,118 on at

Like (0)

Report

It is totally depend on how you want to analyze the data. If you want to analyze data then best is to tag dimensions to it as "Dimension by Analysis" is a great tool in Microsoft Dynamics NAV. It is actually a one strong point in NAV.

I do not see an issue brining customer related details to Dynamics NAV as you said Microsoft Dynamics NAV can handle the data load without an issue.

Was this reply helpful? Yes No
Suggested answer

Tharanga Chandrasekara 23,118 on at

Like (0)

Report

Addition to that I do not understand the part of "payments will be imported against the property dimension, instead of customer dimension".

I think payments should be bring into Microsoft Dynamics NAV against the customer and then tag the property as the dimension to those entries. Otherwise you will not be able to get a proper AR statement from NAV.

Was this reply helpful? Yes No
Suggested answer

Alex A 2,911 on at

Like (0)

Report

Hello,

It sounds like you will have customization around this Housing piece. But, however you decide to import the data, you just need to be sure that the foreign keys are in place. For example, if the payments are imported against the property dimension, then each record should also contain the customer number in one of the fields. If you have that customer number stored in the same table as the property payments then it will be no problem to make customer based reports.

Was this reply helpful? Yes No
Suggested answer

Amol Salvi 18,698 on at

Like (0)

Report

Basically you can upload the transactions for customer id with invoice and payment details

You need to user General journal screen to upload the transactions and you need to prepare the data according to NAV format and use rapidstart/XMLPORT to import into the same

Prior to import you need to create all customer and posting group i.e. Master Data

Hope this will help you

Was this reply helpful? Yes No
Jag S 214 on at

Like (0)

Report

Thanks. But why did the MS Partner didnt want to bring in customer level data from housing system.

Was this reply helpful? Yes No
Suggested answer

Tharanga Chandrasekara 23,118 on at

Like (1)

Report

Actually that answer should come from the partner. I think it is best to ask the valid reason from them before moving forward. At the end of the day you will be using the system and you should be 100% happy about the solution implement.

Was this reply helpful? Yes No
Suggested answer

Amol Salvi 18,698 on at

Like (0)

Report

Completely Agree with Tharanga,

This answer should come from implementation partner.

Partner should give you excel template in which how they want to get data from other system and can program according to format in Navision.

Was this reply helpful? Yes No
Suggested answer

Tharanga Chandrasekara 23,118 on at

Like (0)

Report

I think it is high time to have a big talk with your partner before moving forward. Otherwise you will end up in a conflict with the partner.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

I'm confused about calling a customer a "dimension".

A customer may have dimensions associated with it, but in and of itself it is a Master Record, not a dimension associated with some other Record.

Is there maybe some issue with importing customers that aren't set up already in NAV? Creating Customer Cards on the fly as it were, or creating a routine to synch the customer masters between the two systems?

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report

I suppose you need to import the data also by a customer itself (not customer "dimension"). Dimensions are analytical breakdowns of the transactions whereas the customer is treated as a separate Master Record as Raokman mentioned, with its own card and related settings.

If you need to process accounts receivables and send invoices to each particular customer from NAV, you would need to have a mapping between Customer IDs in Housing system and NAV system, and then book the payments to certain customer cards in NAV. There is no need to create a "dimension" for customer and fill it with values.

Was this reply helpful? Yes No