We just upgraded from 2021 R2 to 2023 R2 and I noticed a generic inquiry that was throwing an error of: “Operand type clash: datetime2 is incompatible with int” I looked at the DB on both 2021 and 2023 and the field “RequestDate” seems to be datetime2 in both versions. Does anybody know why this statement below would no longer work? If I swap these fields to add a +1 on the “ConfirmedDateTime” it works correctly by adding a day to the date.I have a workaround but I was just curious why this is no longer working or a way to get it to work correctly. =IIf(([SOShipment.ConfirmedDateTime]<=([SOLine.RequestDate] + 1)), 1, 0) Thanks
I’m having trouble figuring out the code to allow me to modify the workflow of preventing a field from becoming disabled at shipment confirmation. The field I want to allow edit’s is ISPSUCC128 Here is the code I’m attempting to use but I’m getting a validation error public class SOShipmentEntryExt : PXGraphExtension<SOShipmentEntry> { protected virtual void SOShipment_RowSelected(PXCache cache, PXRowSelectedEventArgs e, PXRowSelected InvokeBaseHandler) { InvokeBaseHandler?.Invoke(cache, e); SOShipment row = e.Row as SOShipment; if (row != null) { Base.Document.Cache.AllowUpdate = true; PXUIFieldAttribute.SetEnabled<SOPackageDetailEx.ISPSUCC128>(cache, row, true); } } } Thanks,Justin
What’s everyone doing to prevent running out of numbers on auto number sequencing.In particular with sales orders...we have a numbering sequence of SA00000 through SA99999 which we are into our SA99XXX so we will run out of numbers soon. Should I just add another digit to this or should I use start dates with different sequences?I’ve run into this in the past already with production tickets and invoices where I just added another digit to give me 999,999 numbers before running out. Thanks
We recently started scanning production tickets from operation to operation, in doing so we had some users who were incorrectly scanning operations in multiple times.ie. A production ticket called for 100 on operation 10 and 20 but say they scanned 500 in for operation 10 and 100 for operation 20 which would then complete the production ticket but also cause a variance (We are backflushing labor/overhead and materials and also Standard Cost on items) We’ve been running cycle counts to correct the raw materials but not sure what else we can do to fix this.We now have a very high balance in our WIP Variance Account which I believe is overstating our cost of goods. I can’t think of a way in the system to correct this since all of these production tickets are closed.I’m no financial guru so I may be thinking about this incorrectly. But our cost of goods the last 2 months have been extremely high. Looking for any help to sort this out. Thanks!
Is there a timeline that an ISV is required to supported the latest revision of Acumatica? I’m wanting to upgrade to Acumatica 2023 R2 but I have a key ISV that has only released support for 2023 R1. Two months seems like more than ample time to release R2 support. Thanks,Justin
I have what I believe is a pretty simple business event. That rounds invoice lines for a specific customer for EDI purposes. However it only seems to trigger when a single line is added and fails to trigger when an invoice has more than 1 line on it. So basically it only triggers when a single record is inserted and doesn’t trigger when 2 or more are inserted.Any ideas on why this fails? Thanks
What is the best way to handle an item that is being discontinued but would like to cross reference to a different item for sales orders. Would “Related Items” be the only way to handle this or is there a difference way? Using Related Items doesn’t seem to work if the item is set to “inactive”. Thanks,Justin
We are trying to do our physical inventory from an excel spreadsheet import using an import scenario but for some reason my scenario will not add another line until it gets to a location with a different ID. I’ve tried changing the orders around and playing with the commit option but I’m not having any luck. I need to use the ADD dialog box in the physical inventory review or count screen as many of our inventory lines don’t have a line at the time of PI creation.(Long explanation).
Trying to update specific sales order lines to add a 10% discount. Which I thought would be a pretty straight forward import but I keep getting an error “View name: Documet” and I can’t figure out what in the import scenario is wrong? Can someone help me out on this one. Attached is the import scenario XML Thanks
I’m working on converting our costing method and testing the results in a test system, but I’m running into interesting results. So I’m looking for some recommendations on what we should do or what could be causing these issues?I have issued out 100% of our inventory so that our inventory balance and valuation are 0 on both reports. But our trial balance is showing values in multiple inventory accounts.I have closed/cancelled out all production orders that were in a “In Process” status. I would expect this to bring all WIP accounts to $0, but again multiple accounts are showing values in there. Since I believe all of these accounts should be at $0 now should I clean these up and bring them down to $0 or am I missing something? I can’t tell exactly when these accounts stopped matching and I’m wondering if they were never tied out correctly from our go live. Thanks for any help.
What is the best way to take inventory to 0 when trying to change your costing method on many items? Trying to do it via adjustments is a little difficult since you have to match qty left on hand by receipts. My thought is I would be able to do this via Inventory > Issues Thanks for any help
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.