Sage 100

I'm stumped.  I have an import into BOM where all I am doing is updating an existing component's quantity.  It is not an option bill, just a regular bill.  I created an export file from BOM detail for the component I need to update, and have included the LineKey in the export and am using that LineKey to reimport.  I've done this lots of times before with the Sales Order file and have had no problems importing into existing lines.  I just don't get why the BOM reimport of an existing component tells me that the record I'm trying to import is not on file.  I'm on version 2018 so this should be doable.  Either I'm just completely blind and having a senior moment, or there is some secret trick with BOM reimporting that I don't know about.

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------

Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

Sometimes I have to make a temp field to Replace with my source column and then point the Sage 100 field to the temp field instead of going direct. I usually have to do that with UDFs but that would be easy enough to try.

------------------------------
Amber Prayfrock, Blytheco
------------------------------

Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

Remove the ItemCode from the import... it cannot be changed, and might be giving false errors.  If all you are doing is updating quantity, try just Bill, Revision, LineKey and the new quantity.

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

Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

I found one problem - the providex.dde LineKey was set to 1 (non-importable), so I changed that to 0.  Now the message I get is "you cannot key column LineKey$ while in edit state".  That message occurs during the real import (not just the test) and even removing the item code from importing this message still occurs.  Actually, I can't remove the item code from the import because the message on that says ​"This Component item already exists.  Do you want to modify it?"  Something is really wrong here.  This shouldn't be this hard.

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------

Original Message:
Sent: 08-13-2020 13:59
From: Kevin Moyes
Subject: Cannot import change to existing BOM item

Remove the ItemCode from the import... it cannot be changed, and might be giving false errors.  If all you are doing is updating quantity, try just Bill, Revision, LineKey and the new quantity.

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


Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

I thought this may have something to do with importing the asterisks for Revision via 'replace' from source file, but it appears you have that in place (i.e. column in csv).

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------

Original Message:
Sent: 08-13-2020 14:12
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

I found one problem - the providex.dde LineKey was set to 1 (non-importable), so I changed that to 0.  Now the message I get is "you cannot key column LineKey$ while in edit state".  That message occurs during the real import (not just the test) and even removing the item code from importing this message still occurs.  Actually, I can't remove the item code from the import because the message on that says ​"This Component item already exists.  Do you want to modify it?"  Something is really wrong here.  This shouldn't be this hard.

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------


Original Message:
Sent: 08-13-2020 13:59
From: Kevin Moyes
Subject: Cannot import change to existing BOM item

Remove the ItemCode from the import... it cannot be changed, and might be giving false errors.  If all you are doing is updating quantity, try just Bill, Revision, LineKey and the new quantity.

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


Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

FWIW - I have never been able to import to the BOM file. I do this often for a couple of clients and end up dumping the entire file, reinitialize, then re-import with changes.

------------------------------
Greg Stiles
S & W Microsystems
Torrance CA
310.787.1010
------------------------------

Original Message:
Sent: 08-14-2020 11:27
From: Brett Zimmerman
Subject: Cannot import change to existing BOM item

I thought this may have something to do with importing the asterisks for Revision via 'replace' from source file, but it appears you have that in place (i.e. column in csv).

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------


Original Message:
Sent: 08-13-2020 14:12
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

I found one problem - the providex.dde LineKey was set to 1 (non-importable), so I changed that to 0.  Now the message I get is "you cannot key column LineKey$ while in edit state".  That message occurs during the real import (not just the test) and even removing the item code from importing this message still occurs.  Actually, I can't remove the item code from the import because the message on that says ​"This Component item already exists.  Do you want to modify it?"  Something is really wrong here.  This shouldn't be this hard.

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:59
From: Kevin Moyes
Subject: Cannot import change to existing BOM item

Remove the ItemCode from the import... it cannot be changed, and might be giving false errors.  If all you are doing is updating quantity, try just Bill, Revision, LineKey and the new quantity.

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


Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

BOI works for me to replace existing record/fields for this table.

------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642
------------------------------

Original Message:
Sent: 08-13-2020 14:12
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

I found one problem - the providex.dde LineKey was set to 1 (non-importable), so I changed that to 0.  Now the message I get is "you cannot key column LineKey$ while in edit state".  That message occurs during the real import (not just the test) and even removing the item code from importing this message still occurs.  Actually, I can't remove the item code from the import because the message on that says ​"This Component item already exists.  Do you want to modify it?"  Something is really wrong here.  This shouldn't be this hard.

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------


Original Message:
Sent: 08-13-2020 13:59
From: Kevin Moyes
Subject: Cannot import change to existing BOM item

Remove the ItemCode from the import... it cannot be changed, and might be giving false errors.  If all you are doing is updating quantity, try just Bill, Revision, LineKey and the new quantity.

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


Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

@Jane Scanlan have you resolved this issue, is it still "urgent"?
​​

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------

Original Message:
Sent: 08-17-2020 19:10
From: Dan Burleson
Subject: Cannot import change to existing BOM item

BOI works for me to replace existing record/fields for this table.

------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642
------------------------------


Original Message:
Sent: 08-13-2020 14:12
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

I found one problem - the providex.dde LineKey was set to 1 (non-importable), so I changed that to 0.  Now the message I get is "you cannot key column LineKey$ while in edit state".  That message occurs during the real import (not just the test) and even removing the item code from importing this message still occurs.  Actually, I can't remove the item code from the import because the message on that says ​"This Component item already exists.  Do you want to modify it?"  Something is really wrong here.  This shouldn't be this hard.

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:59
From: Kevin Moyes
Subject: Cannot import change to existing BOM item

Remove the ItemCode from the import... it cannot be changed, and might be giving false errors.  If all you are doing is updating quantity, try just Bill, Revision, LineKey and the new quantity.

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


Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

@Moira Goggin this is not resolved, but it can be moved.  I'll have to figure out what is wrong ... maybe their dictionaries.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------

Original Message:
Sent: 08-18-2020 10:34
From: Moira Goggin
Subject: Cannot import change to existing BOM item

@Jane Scanlan have you resolved this issue, is it still "urgent"?
​​

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------


Original Message:
Sent: 08-17-2020 19:10
From: Dan Burleson
Subject: Cannot import change to existing BOM item

BOI works for me to replace existing record/fields for this table.

------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642


Original Message:
Sent: 08-13-2020 14:12
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

I found one problem - the providex.dde LineKey was set to 1 (non-importable), so I changed that to 0.  Now the message I get is "you cannot key column LineKey$ while in edit state".  That message occurs during the real import (not just the test) and even removing the item code from importing this message still occurs.  Actually, I can't remove the item code from the import because the message on that says ​"This Component item already exists.  Do you want to modify it?"  Something is really wrong here.  This shouldn't be this hard.

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:59
From: Kevin Moyes
Subject: Cannot import change to existing BOM item

Remove the ItemCode from the import... it cannot be changed, and might be giving false errors.  If all you are doing is updating quantity, try just Bill, Revision, LineKey and the new quantity.

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


Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant

Thread moved to Sage 100 community.

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------

Original Message:
Sent: 08-18-2020 10:43
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@Moira Goggin this is not resolved, but it can be moved.  I'll have to figure out what is wrong ... maybe their dictionaries.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------


Original Message:
Sent: 08-18-2020 10:34
From: Moira Goggin
Subject: Cannot import change to existing BOM item

@Jane Scanlan have you resolved this issue, is it still "urgent"?
​​

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.


Original Message:
Sent: 08-17-2020 19:10
From: Dan Burleson
Subject: Cannot import change to existing BOM item

BOI works for me to replace existing record/fields for this table.

------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642


Original Message:
Sent: 08-13-2020 14:12
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

I found one problem - the providex.dde LineKey was set to 1 (non-importable), so I changed that to 0.  Now the message I get is "you cannot key column LineKey$ while in edit state".  That message occurs during the real import (not just the test) and even removing the item code from importing this message still occurs.  Actually, I can't remove the item code from the import because the message on that says ​"This Component item already exists.  Do you want to modify it?"  Something is really wrong here.  This shouldn't be this hard.

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:59
From: Kevin Moyes
Subject: Cannot import change to existing BOM item

Remove the ItemCode from the import... it cannot be changed, and might be giving false errors.  If all you are doing is updating quantity, try just Bill, Revision, LineKey and the new quantity.

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


Original Message:
Sent: 08-13-2020 13:15
From: Jane Scanlan
Subject: Cannot import change to existing BOM item

@David Speck II,

I have a screen shot attached of the data tab of the VI job, and yep I am replacing the linekey with field number 3 in the source file.  I've opened the source file in notepad and the leading zeroes are all there, and field 3 is correct.  I checked all these things before posting my initial request for help. I've now attached the .csv file to this post.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 08-13-2020 13:06
From: David Speck II
Subject: Cannot import change to existing BOM item

On the data tab, is your line key using the replace operation?

If not, it must use the replace operation so your source file must contain it as well.

I would double check that the source file and VI job delimiter and column order are in sync. 

Then check for any missing characters from numeric fields, such as leading zeros if the source was opened in excel.

Make sure you don't have any extra trailing characters in the source as well that might be causing the import to not see the source as the same as the record in sage 100.

Thanks

David Speck

TSS

Sage | Sage 100 Certified Consultant