FlowField not calculating correctly in EDI

KimDyn

I am creating an outbound 810 EDI invoice in the lovely Lanham EDI module. It contains a FlowField in the Sales Invoice Header table. The FlowField sums the line amount with a where clause based on a field being checked. We will call this FlowField XField. I have mapped the XField into my 810 and generated an EDI file. When I look at the EDI file the XField is not correct. I looks like EDI bypassed the WHERE clause in the FlowField CalcFormula.

Any Help???? ](*,)

Thanks!!

Kimberly

Alex_Chow

Is this a new flowfield that you've created?

If so, just modify codeunit 14002350 and put the calcfields to the respective function.

Savatage

I don't have that codeunit # myself (Using Gen1)

Alex_Chow

Savatage wrote:

I don't have that codeunit # myself (Using Gen1)

it's a good idea to upgrade to Gen 2. IMHO, it's much more flexible and much more powerful on how it handles EDI documents for multiple trading partners.

David_Singleton

Alex Chow wrote:

Savatage wrote:

I don't have that codeunit # myself (Using Gen1)

it's a good idea to upgrade to Gen 2. IMHO, it's much more flexible and much more powerful on how it handles EDI documents for multiple trading partners.

yeah Gen one has just too many limitations.

Personally I would love to see Gen one just removed, I really can not stand that EDI vs E.D.I bullS##t.

David_Singleton

KimDyn wrote:

I am creating an outbound 810 EDI invoice in the lovely Lanham EDI module. It contains a FlowField in the Sales Invoice Header table. The FlowField sums the line amount with a where clause based on a field being checked. We will call this FlowField XField. I have mapped the XField into my 810 and generated an EDI file. When I look at the EDI file the XField is not correct. I looks like EDI bypassed the WHERE clause in the FlowField CalcFormula.

Any Help???? ](*,)

Thanks!!

Kimberly

Are you on (or did you move) to SQL.

There are some keys that need to be changed if you did the move. Specifically if you went from 4.00 Native to 5.00 SQL executables.

Alex_Chow

David Singleton wrote:

Personally I would love to see Gen one just removed, I really can not stand that EDI vs E.D.I bullS##t.

Word. =D>

KimDyn

Is this a new flowfield that you've created?

If so, just modify codeunit 14002350 and put the calcfields to the respective function.

This worked great!!! Thank you very much for the help Alex. =D>

I am on Gen 2 and running the SQL option.

Again, thanks for your help!

Kimberly

KimDyn

Are you on (or did you move) to SQL.

There are some keys that need to be changed if you did the move. Specifically if you went from 4.00 Native to 5.00 SQL executables.

We are still running 3.6 :sick: But I will keep this in mind as we are starting to get ramped up for a upgrade to 5.0. Thanks for info.
[/quote]

Alex_Chow

You're welcome! Always glad to be of service.

Please mark the topic as [SOLVED] so this thread can help other people as well.

eknraw

Alex, great suggestion modifying codeunit 14002350. I went one step further and modified the 'Load E.D.I. Navision Fields' report that generates the code in 14002350 so that if someone ever did go back and regenerate the map codeunit the flowfield code would always be there.

This is in the CreateCode() function. Hopefully, you can find the bit by the surrounding code.

Report 14002350
**SNIP**
WriteLine(' PROCEDURE MapExp@1();');
WriteLine(' BEGIN');
//>> START
//Added for flowfield to external document
WriteLine(' SalesLine.CALCFIELDS("UPC Cross Ref No.");');
//>> END
WriteLine(' CASE EDIElement."NAV Table No." OF');
**SNIP**

Hope this helps someone.

Bill

Alex_Chow

Awesome! Thanks for sharing. You are one cool dude! 8)