Dynamics 365 Business Central/NAV User Group

Hi Erik. What kind of mess do you mean could happen? I would not want to force currency code to be used for all transactions. But if our LCY Code is 'EUR' then normally Currency Code would be left blank on sales documents (=edfault LCY code). Only for some types sales document we would use a different Currency Code, the code could for example be "EUR_CASH" only to achieve a different kind of invoice and line amount rounding.

Hi Gary, Try with a VAR in the L_WhseEntry parameter.

Did you rename the fields? Did you check in SQL, that the field is actually there?

the field is not there.

Here's what's happening on this week's live webcast schedule. Register to attend live or get access to the recorded event. Tuesday, October 24, 2017 Solve Document Challenges and Improve Customer Engagement with Xpertdoc and Dynamics 365! 12:00 PM EDT Register Are you a Dynamics 365/CRM user looking to solve your business' document challenges? Join Xpertdoc Channel Manager read more ...read more

Something similar happened to me once. Don't exactly remember how it happened, but it was something about renaming the field. Have you tried to synchronize the tables? That was a new "feature" in NAV 2013 R2, and I'm sure it is related. I think I ended up having to delete the table and add it again, it was not easy to get rid of. So I hope it is not in your production database?

Yes ，VAR in the L_WhseEntry parameter is ok, I just don't know the reason why i pass the NONE-VAR parameter can not pass its filter?

Thanks Erik, I got it. Hope you everything goes well, My friendly teacher, You helped me a lot. I am a "Question-boy".

Deleting table is not possible for me and to add it again is not possible for me.

So you did it in production? [:#]

Then make a backup of the database, and try what I say. Import the table as it was before and then create your field again. And of course make sure that you're on the latest CU of NAV 2013 R2. This problem was as far as I know fixed, at least I never saw it again since.

Did you try: That's "the documentation" available for Microsoft Power BI.

Hi Brahim, What are you trying to open the NAV 2013 database with? The Development Environment or the Windows Client? Did you complete the upgrade process, run the upgrade codeunits etc.? Or where are you in the process? And which local version are you upgrading to?

Hi Eric, I'm trying to open the NAV 2013 database on the Development Environment of NAV 2017 version (10.0.17972).I'm currently blocked in the task of converting the old database to the Microsoft Dynamics NAV 2017 format. this step comes directly after deleting all objects except tables from the old database. the problem is among the standard and customised tables there are tables with ID between 33 000 000 and 33 000 999 wich was added by another integration company. i'm facing problems deleting completely these tables from the database because i'm doubting that those are calling the codeunit mentionned in my question.

Hi KR, Exactly what doesn't work? Are yo able to make a partial prepayment? And which version of NAV?

Hi Brahim, 7.00 = NAV 2013 7.10 = NAV 2013 R2 8.00 = NAV 2015 9.00 = NAV 2016. Hope that answers your question. [:)]

Yes it does. Thank you. :)

#nav2018 #dynamics365 #tenerife #webcast #learn4nav Hallo zusammen, Christian Hauptmann startet heute mit einem ersten Überblick zur nächsten Version von „NAV 2018“ Neuerungen in der Anwendung. Wer selbst einen Blick in einige neue Features werfen möchte, kann dafür die Developer Preview ...read more

Forum Post: RE: Invoice Rounding, using LCY Currency Code in Currency table

Forum Post: RE: Record Parameter in function lost filters?

Forum Post: RE: Invalid Column name error

Forum Post: RE: Invalid Column name error

Blog Post: Microsoft Dynamics Webcasts, October 23-27, 2017: D365 doc management; AWS for ISVs; Sales Navigator lead gen; Migrating AX, NAV, GP, SL to cloud

Forum Post: RE: Invalid Column name error

Forum Post: RE: Record Parameter in function lost filters?

Forum Post: RE: how to add a key into query ?

Forum Post: RE: Invalid Column name error

Forum Post: RE: Invalid Column name error

Forum Post: RE: Invalid Column name error

Forum Post: RE: Invalid Column name error

Forum Post: RE: MS PowerBI

Forum Post: RE: Error codeunit not found while converting 2013 database in nav 2017

Forum Post: RE: Error codeunit not found while converting 2013 database in nav 2017

Forum Post: RE: Invalid Column name error

Forum Post: RE: Advance Payment to Vendor

Forum Post: RE: wich fob from the ugrade toolkit should i import in data conversion nav 2013 to nav 2017?

Forum Post: RE: wich fob from the ugrade toolkit should i import in data conversion nav 2013 to nav 2017?

Blog Post: Learn4NAV: Heute 10:30 „NAV 2018“ Neuerungen in der Anwendung – Ein Überblick