Wow! Great work! Nice to see the updated materials for Field Service.
Thank you for posting the solution - this helped me today!
Thank you @Naveen B and @praveenpo this is helpful to find the individual build release notes in one place. What would be nice is if Acumatica put these in a cumulative document so that one could open one document to scan or search for all build release notes for a version either grouped by build, or by module with the build the issue was fixed in. It would make it much easier to scan prior to creating a support case.
@Naveen B I did look at that file briefly but isn’t that just the initial release notes and not the cumulative release notes for all subsequent builds?To provide a little more context, say a customer is on build 20.214.0030 and we encounter a bug in the Prepare Physical Inventory process. Prior to creating a support case, if I wanted to check the release notes for everything after build 20.214.0030 to see if this issue was already fixed in a subsequent build, currently I would need to open and scan through each build’s release notes from 20.215.xxxx to 20.221.xxx correct?What I was hoping for was to go to a webpage or pdf that had all the release notes for all builds in one place to make the search for fixes rather than having to download, open and search through multiple documents.
Thank you @vkumar that is very helpful - I was wondering if all the items in the release notes for each build made it to this list or not, but I will take “most” as the best answer! Much quicker than searching individual release notes.
In one of our cases this was due to the having the auto set to Process All when there was a condition to only process one of the system email accounts in the schedule. Changing it to Process instead resolved the error.
I agree with the requested as initially raised by Greg and am encountering this exact issue at a client. Reorder Point is the point that should trigger re-ordering to the Max Qty as the default replenishment does. Otherwise MRP is to noisy and keeps recommending to build small qty’s each time some are sold. When the reorder point is hit it should trigger demand to re-stock to the max qty.
You could create a bank entry type for these an record as a bank entry or you could process as a Cash Sale if you want to create a customer to track who gave you the money or create a CASH or DONOR customer to use when recording donations.
I am not sure which option you prefer of the two provided.For the first one, in Banking - Preferences open the Entry Types screen and create a new receipt entry type for this linked to the GL account and subaccount that you want the amount to be posted to.Then go to the cash account that you are wanting to deposit this to and add the new entry type on the Entry Types tab and Save.Lastly, go the Cash Transactions screen and record the receipt to the cash account using the entry type you created and release the transaction.For the second option of entering this via AR, create a new customer and record the transaction in Receivables - Transactions - Cash Sales.
Ray, requirements can be found here:https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=a8d5d39d-513a-4f93-b484-a95eb33103a1.Net Required:
@ray20 - no other issues but keep in mind that this is just in a local test virtual machine and not in a production environment at this time.
Lots of options - I use AirParrot for live display of my iPhone on my notebook for demo and training purposes.
@Chris Hackett - No I have not yet. It is just for local test data so no as critical at the moment but will be when we start moving our on premise clients to 2023 R1 or higher. I may have to create a case I guess.
James, thank you for the detailed response - much appreciated!My understanding is that the new archive feature in 2023 R1 uses SQL partitions.While most of the clients we work with are on Acumatica’s SaaS environment, we have a small number of clients that are on premise for a variety of reasons, most of which are not going to be running the Enterprise Edition of SQL server.There is no mention of this edition of SQL server being required in the online help:https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=a8d5d39d-513a-4f93-b484-a95eb33103a1Currently, the on-premise clients that I work with are on 2022 R2 so it has not been an issue yet, but looks like it may be for the next upgrade.
The solution in my case was to install SQL Server 2016 PU3 and then then latest CU. Acumatica 2023 R1 installed without any partition function complaints.
The root cause here is calling the same report as the main report in a subreport.
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.