Hi @naveenb74,Thanks for your suggestion, I was able to implement that and worked fine.Have a great day.
Hi @Naveen B,Thanks so much, I followed the steps and it worked great, Have a nice day!
It is possible to update the data between tenants, but the specific recommendation should be based on the nature of the data. For general case, I’d say the best way is to utilize import/export scenarios to export data to excel file and import it back. Thanks for your answer @Dmitrii Naumov One of our client’s requirements is that when the vendor is saved in Vendors screen of one Tenant, the entire document has to update the same vendor from another tenant right away.
@alejandroalvarado64 in that case I’d suggest something like calling REST API of the another tenant. You can trigger the REST API call using business events/push notifications in the source tenant. I’m going to go deeper into those topics! Thanks for the guide @Dmitrii Naumov
@alejandroalvarado64 in that case I’d suggest something like calling REST API of the another tenant. You can trigger the REST API call using business events/push notifications in the source tenant. I’m going to go deeper into those topics! Thanks for the guide @Dmitrii Naumov Hi @alejandroalvarado64 We’re doing this for master data such as stock items. When users create on one tenant as master, will duplicate in other tenants. My teams using API to do this. So i think that’s the best approach. Daru Thanks for your recommendation @purwandaruw47, surely API is the best way
Try this. To see all records of your custom DAC regardless of the company or branch that you are logged in, you will need to change the branchID field in your custom DAC to the PXUnbound attribute. This attribute tells Acumatica that the field should not be bound to the database column and should not be used in any database queries. Here is an example of how you can change the branchID field in your custom DAC: [PXUnbound]public virtual int? BranchID { get; set; }public abstract class branchID : PX.Data.BQL.BqlInt.Field<branchID> { } Additionally, you will need to update any views or queries that use the branchID field to ignore it and not include it in their filters or where clauses. It is also important to note that using the PXUnbound attribute may have security implications and can potentially expose sensitive data. Therefore, it is recommended to carefully consider the potential security risks before implementing this solution. Thanks for your answer @Yuriy Zaletskyy,I hav
Already have an account? Login
Enter your 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.