Prev: Restrict user to access company
Next: Bill of lading in navision
From: Shelley on 26 Apr 2010 08:42
We are experiencing the same message. However, the customers are not over their credit limit. When trying to create a sales order for a route delivery customer, we use a "zip code lookup" to determine what day of the week we are in their area. We receive the error then. We also receive it when we are setting up a new customer on a new route.



hitendr wrote:

Re: Navision importing invoices issue
01-May-08

Hi Guys,

Thanks for the posts.

We have been able to identify the problem, the error was coming up because
of the Credit Warning window which was being launched once a company exceeds
it's limit and it wasn't specific while doing it through the dataport. We
have disabled the warning messages and all works fine.

Thanks for your help once again.

Regards

Hitendra

"Vishal" wrote:

Previous Posts In This Thread:

On Tuesday, April 29, 2008 11:33 AM
hitendr wrote:

Navision importing invoices issue
Hi,

I am programmer by profession and am new to navision. We had a requirement
to import invoices generated on our CRM system directly to navision.

I would go bit in detail here, we have built a dataport to import invoices
to navision from our CRM system. Now the dataport includes 3 tables, Sales
Header, Sales Lines & Document Dimension, we create a csv file to match the
dataport and the invoices were being imported fine for a month. After a lot
of debugging the posting of the inovices also works perfectly. But we
stumbled into to a problem now, when we try to import a new invoice for the
same customer (whose invoice was posted successfully last month), the import
gives the following error:

---------------------------------------
The following C/AL functions can be used only to a limited degree during
write transactions (because one or more tables will be locked).

Form.RunModal() is not allowed in write transactions.

CodeUnit.Run() is allowed in write transactions only if the return value is
not used. For example, 'OK := CodeUnit.Run()' is not allowed.

Report.RunModal() is allowed in write transactions only if 'RequestForm =
FALSE'. For example, 'Report.RunModal(...,FALSE)' is allowed.

DataPort.RunModal() is allowed in write transactions only if 'RequestForm =
FALSE'. For example, 'DataPort.RunModal(...,FALSE)' is allowed.

Use the COMMIT function to save the changes before this call, or structure
the code differently.
---------------------------------------

Not sure what this error means, we are trying to frantically look around for
a solution. Would appreicate if one of you guys can possibly help us with
this.

Thanks and regards

Hitendra

On Wednesday, April 30, 2008 2:52 AM
redfox_ne wrote:

RE: Navision importing invoices issue
- Where is the debugger stop?

- Did you tryed to import data & delete data-lines step-by-step in the
source file?

"hitendra" wrote:

On Wednesday, April 30, 2008 3:31 AM
hitendr wrote:

RE: Navision importing invoices issue
Hi,

Thanks for the reply. Pardon my ignorance but can you please guide us how we
can use a debugger on the Navision Dataport, this might help us track the
issue where it stems.

Also, as suggested we tried importing it one by one table and found that the
error was because of the "CallFieldValidate" was enabled for fields
SellToCustomer & BillToCustomer for the Sales Header table in the dataport.
But this option will give an error (when checked) only while trying to import
invoices for companies who already have a posted invoice in the "Sales
Invoice Header" table.

I know disabling the CallFieldValidate check is not advisable, can you
please suggest what the problem might possibly be. Or is there a way to check
what does the CallFieldValidate function for SellToCustomer actually does,
does it look for a key or something why it gives the error?

Thanks


"RedFox" wrote:

On Wednesday, April 30, 2008 3:34 AM
hitendr wrote:

RE: Navision importing invoices issue
Hi,

Thanks for the reply. Pardon my ignorance but can you please guide us how we
can use a debugger on the Navision Dataport, this might help us track the
issue where it stems.

Also, as suggested we tried importing it one by one table and found that the
error was because of the "CallFieldValidate" was enabled for fields
SellToCustomer & BillToCustomer for the Sales Header table in the dataport.
But this option will give an error (when checked) only while trying to import
invoices for companies who already have a posted invoice in the "Sales
Invoice Header" table.

I know disabling the CallFieldValidate check is not advisable, can you
please suggest what the problem might possibly be. Or is there a way to check
what does the CallFieldValidate function for SellToCustomer actually does,
does it look for a key or something why it gives the error?

Thanks


"RedFox" wrote:

On Wednesday, April 30, 2008 5:05 PM
Vishal wrote:

Re: Navision importing invoices issue
from the menu bar - click Tool - Debugger and remove the "Breakpoint on
Triggers" and again Tool - Debugger and Select the "Active" to make it stop
at the error line.

--

Regards
Vishal
http://www.dynamicsnation.com
Microsoft Dynamics - Partners, Customers, Addons, Jobs, Discussion - All
FREE

"hitendra" <hitendra(a)discussions.microsoft.com> wrote in message
news:F4F14B6F-C3ED-41E6-9C4B-9433ED7867A0(a)microsoft.com...

On Thursday, May 01, 2008 5:51 AM
hitendr wrote:

Re: Navision importing invoices issue
Hi Guys,

Thanks for the posts.

We have been able to identify the problem, the error was coming up because
of the Credit Warning window which was being launched once a company exceeds
it's limit and it wasn't specific while doing it through the dataport. We
have disabled the warning messages and all works fine.

Thanks for your help once again.

Regards

Hitendra

"Vishal" wrote:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Excel 2007 Filter Tool
http://www.eggheadcafe.com/tutorials/aspnet/ae703d26-58da-423a-a2cb-1f3a46fbea8f/excel-2007-filter-tool.aspx
 | 
Pages: 1
Prev: Restrict user to access company
Next: Bill of lading in navision