We’ve been able to resolve our issue with importing BOMs. It seems there are various fields that are required on every line and you have to pay close attention to the demo Excel sheet as to which ones they are.
@Evan G or @jmckinnon Did either of you ever get a BOM import scenario working? We’re trying to use the standard Import Scenario and aren’t having much success.We are able to import a BOM with a single operation and a single material, but not multiple operations or multiple materials.
Hi @Freeman Helmuth I tried to use the Increase Column length option under the Database script to increase the field length of the UOM field from the AMBomMatl table. Not getting any error. Its working fine. May be causing issue with some other customization. Can you please cross check the customization once? you have to customize the DAC as wellDo that and let me know what your results are
@Naveen B So it seems.However this error occurs when doing nothing but the following in a customization:Add the database script to extend the DB field:Using:[PXRemoveBaseAttribute(typeof(PXDBStringAttribute))][PXDBString(80, IsUnicode = true)]to modify the DAC: My DACs show customized properly in the DAC browser and the field lengths show correct-so why this odd error?
@Naveen B Yes this is what we are doing, and we have all those other tables done already. Like I said, this is a field the previous developer missed when doing those, and I can’t figure out how to extend this one. I’ve modified the DAC with the following: But then I get this error: And FYI: It is worth it to us. We have many different UOMs that we use to count and to receive in. Honestly its a bit ridiculous that Acumatica has this restriction. I have an open feature request for it.
@Ellie Can you post the accounting transactions for this? What account is credited when the landed cost is released? Is it the same one that the non-stock item posts to?
I have the same question on this
Update: Don't try MySQL 8.0+ Stick with 5.7. It works great.We've downgraded and the issue went away
For some reason my images of the collations are not postingI’ve tried setting up the database/table/column collations as UTF8, utf8mb4, latin1 and several others with 0% success. Per another members research, this may be an issue with the way columns are named in MySQL. Acumatica is using a MySQL reserved name:
Can you just use the Cash Account Details GI to feed that? CA303000
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.