Skip to main content
Answer

Adding Operation ID line to import scenario creates Key: OperationCD when I want Line Number=-1

  • January 25, 2024
  • 3 replies
  • 212 views

Forum|alt.badge.img

Setting up import scenario similar to out of the box ACU Import BOM. But I can’t seem to add the Operation ID → Operation ID line without it adding the <Key: OperationCD> field. I need the <Line Number> = -1 field, same as ACU Import BOM.

 

What am I doing wrong here? I want to add lines for these operations, not key on them to add materials.

 

ACU Import BOM - Out of the Box

 

Me - unable to add Operation ID line without the Key line above.

 

Best answer by jwarren

Looks like this worked just fine - not sure I was getting the error originally

 

 

3 replies

jharris
Semi-Pro I
Forum|alt.badge.img+7
  • Semi-Pro I
  • January 25, 2024

What exactly are you trying to accomplish?  Inactivating the OperationCD as a key in an import scenario could potentially resolve the issue if OperationCD is not necessary for the operation you are trying to perform. In Acumatica, the key fields are used to identify unique records for updates. If your intent is to insert new records rather than update existing ones, then OperationCD might not need to be a key field.


Forum|alt.badge.img
  • Author
  • Semi-Pro I
  • January 25, 2024

I’m just trying to add four operations/Work Centres, with associated line details (run units, run time), to the BOM. 

 

001 - Work Centre A

002 - Work Centre B

003 - Work Centre C

004 - Work Centre D

 

I don’t believe that OperationCD needs to be a key field (because I’m trying to add these lines) but I’m unable to delete it or prevent the row <Key: OperationCD> from being included when adding the line below it Operation ID = Operation ID.

 

And I’m scratching my head because I can see the out of box scenario ACU Import BOM is able to add the operation ID = operation ID without the <key> field without any issues.

 

I’ve tried inactivating the <Key> line but import by scenario giving error.

 

 

 


Forum|alt.badge.img
  • Author
  • Semi-Pro I
  • Answer
  • January 26, 2024

Looks like this worked just fine - not sure I was getting the error originally