Sage 100

V2019 Advanced - I'm importing into existing sales order line-items to update the Sales and COGS accounts due to changes in the item product line assignments. Importing into the linekey fields has always worked for me in the past, but today the linekey field was not being read - it was completely passed over, not listed in the VI log record detail. In providex.ddf I changed the linekey field 20 to ReadOnly = 0. Now the import is reading the LineKey field but reporting it in the log as an invalid imported field with the message "You cannot set key column Linekey$ while in Edit state.." I found a KB article (dated yesterday!) stating this is a defect, and that the import should work despite the message. However, that turned out not to be the case: additional items were imported as new line-items rather than the existing items being impacted. Has anyone experienced this and found a way around it?

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------

I tried it just now on a 2019.2 system and it worked. I didn't have to remove the ReadOnly flag from the dictionary either. Now it was important that I did a Replace on the LineKey. If you did it as an Assign that will not work as it will get treated as a new record (EditState 2). Hope that helps.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------

@Alnoor Cassim thank you for testing this.  I'm on PU2 as well.  I tested on my system and got the same results as on the client's system.  Obviously there's a needle in a haystack here!

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------

Does your source file VI job have only the required 4 columns?  SO#, LineKey, GL1, GL2...?  If you try to set ItemCode before LineKey the job likely thinks it's a new line as soon as you do that, and since you are updating, importing the ItemCode is not required at all.
Leading zeroes included in all values?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 11-18-2020 18:13
From: Susan Pawlowic
Subject: Importing Into Existing Lines

@Alnoor Cassim thank you for testing this.  I'm on PU2 as well.  I tested on my system and got the same results as on the client's system.  Obviously there's a needle in a haystack here!

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 11/18/2020 6:21:00 PM
From: Kevin Moyes
Subject: RE: Importing Into Existing Lines

Does your source file VI job have only the required 4 columns?  SO#, LineKey, GL1, GL2...?  If you try to set ItemCode before LineKey the job likely thinks it's a new line as soon as you do that, and since you are updating, importing the ItemCode is not required at all.
Leading zeroes included in all values?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Because it's failing on the LineKey field, it requires an item code (in the absence of a linekey it thinks it's a new line).  However, item code is listed AFTER LineKey and I'm anticipating I can remove itemcode altogether once LineKey is being read.  The operator for LineKey is Replace.  I tried adding a temp field, setting it as a key assign, and bringing in the LineKey then setting the LineKey field to read in the Temp field but no better luck.

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 11-18-2020 18:41
From: Alnoor Cassim
Subject: Importing Into Existing Lines

This is true for me that my test did not include Item Code. Maybe that's the difference.

Original Message:
Sent: 11/18/2020 6:21:00 PM
From: Kevin Moyes
Subject: RE: Importing Into Existing Lines

Does your source file VI job have only the required 4 columns?  SO#, LineKey, GL1, GL2...?  If you try to set ItemCode before LineKey the job likely thinks it's a new line as soon as you do that, and since you are updating, importing the ItemCode is not required at all.
Leading zeroes included in all values?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 11-18-2020 18:13
From: Susan Pawlowic
Subject: Importing Into Existing Lines

@Alnoor Cassim thank you for testing this.  I'm on PU2 as well.  I tested on my system and got the same results as on the client's system.  Obviously there's a needle in a haystack here!

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC

v2019.2

If you try to edit the SO manually, do you get any errors about it being invoiced / picked / edited by someone else?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 11-19-2020 11:08
From: Susan Pawlowic
Subject: Importing Into Existing Lines

Because it's failing on the LineKey field, it requires an item code (in the absence of a linekey it thinks it's a new line).  However, item code is listed AFTER LineKey and I'm anticipating I can remove itemcode altogether once LineKey is being read.  The operator for LineKey is Replace.  I tried adding a temp field, setting it as a key assign, and bringing in the LineKey then setting the LineKey field to read in the Temp field but no better luck.

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------


Original Message:
Sent: 11-18-2020 18:41
From: Alnoor Cassim
Subject: Importing Into Existing Lines

This is true for me that my test did not include Item Code. Maybe that's the difference.

Original Message:
Sent: 11/18/2020 6:21:00 PM
From: Kevin Moyes
Subject: RE: Importing Into Existing Lines

Does your source file VI job have only the required 4 columns?  SO#, LineKey, GL1, GL2...?  If you try to set ItemCode before LineKey the job likely thinks it's a new line as soon as you do that, and since you are updating, importing the ItemCode is not required at all.
Leading zeroes included in all values?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-18-2020 18:13
From: Susan Pawlowic
Subject: Importing Into Existing Lines

@Alnoor Cassim thank you for testing this.  I'm on PU2 as well.  I tested on my system and got the same results as on the client's system.  Obviously there's a needle in a haystack here!

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC

@Kevin Moyes no, I am able to edit the SO lines manually. 
​

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 11-19-2020 11:41
From: Kevin Moyes
Subject: Importing Into Existing Lines

v2019.2

If you try to edit the SO manually, do you get any errors about it being invoiced / picked / edited by someone else?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 11-19-2020 11:08
From: Susan Pawlowic
Subject: Importing Into Existing Lines

Because it's failing on the LineKey field, it requires an item code (in the absence of a linekey it thinks it's a new line).  However, item code is listed AFTER LineKey and I'm anticipating I can remove itemcode altogether once LineKey is being read.  The operator for LineKey is Replace.  I tried adding a temp field, setting it as a key assign, and bringing in the LineKey then setting the LineKey field to read in the Temp field but no better luck.

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC


Original Message:
Sent: 11-18-2020 18:41
From: Alnoor Cassim
Subject: Importing Into Existing Lines

This is true for me that my test did not include Item Code. Maybe that's the difference.

Original Message:
Sent: 11/18/2020 6:21:00 PM
From: Kevin Moyes
Subject: RE: Importing Into Existing Lines

Does your source file VI job have only the required 4 columns?  SO#, LineKey, GL1, GL2...?  If you try to set ItemCode before LineKey the job likely thinks it's a new line as soon as you do that, and since you are updating, importing the ItemCode is not required at all.
Leading zeroes included in all values?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-18-2020 18:13
From: Susan Pawlowic
Subject: Importing Into Existing Lines

@Alnoor Cassim thank you for testing this.  I'm on PU2 as well.  I tested on my system and got the same results as on the client's system.  Obviously there's a needle in a haystack here!

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC

This was resolved with @Alnoor Cassim's help.  Apparently the import IS working despite the Invalid Field warning - just as Sage said...feeling a little foolish!
​​

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 11-19-2020 11:54
From: Susan Pawlowic
Subject: Importing Into Existing Lines

@Kevin Moyes no, I am able to edit the SO lines manually.
​

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------


Original Message:
Sent: 11-19-2020 11:41
From: Kevin Moyes
Subject: Importing Into Existing Lines

v2019.2

If you try to edit the SO manually, do you get any errors about it being invoiced / picked / edited by someone else?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-19-2020 11:08
From: Susan Pawlowic
Subject: Importing Into Existing Lines

Because it's failing on the LineKey field, it requires an item code (in the absence of a linekey it thinks it's a new line).  However, item code is listed AFTER LineKey and I'm anticipating I can remove itemcode altogether once LineKey is being read.  The operator for LineKey is Replace.  I tried adding a temp field, setting it as a key assign, and bringing in the LineKey then setting the LineKey field to read in the Temp field but no better luck.

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC


Original Message:
Sent: 11-18-2020 18:41
From: Alnoor Cassim
Subject: Importing Into Existing Lines

This is true for me that my test did not include Item Code. Maybe that's the difference.

Original Message:
Sent: 11/18/2020 6:21:00 PM
From: Kevin Moyes
Subject: RE: Importing Into Existing Lines

Does your source file VI job have only the required 4 columns?  SO#, LineKey, GL1, GL2...?  If you try to set ItemCode before LineKey the job likely thinks it's a new line as soon as you do that, and since you are updating, importing the ItemCode is not required at all.
Leading zeroes included in all values?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-18-2020 18:13
From: Susan Pawlowic
Subject: Importing Into Existing Lines

@Alnoor Cassim thank you for testing this.  I'm on PU2 as well.  I tested on my system and got the same results as on the client's system.  Obviously there's a needle in a haystack here!

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC