Acumatica REST API Error: Inter-Branch Transactions feature is disabled - acumatica

We are using the REST API to create a Sales Order in Acumatica. For some customers we receive the below error message. Not sure why the API is complaining about “inter branch” as we target a single tenant and try to create a sales order for an existing customer under that tenant. (Not sure if branch means something else than “tenant” in this context)
I read the other post on the forum and tried to find the feature for enabling inter branch but that feature was not listed. Can someone please help with this?
Exception: An error occurred during processing of the field Allocated value False Inter-Branch Transactions feature is disabled.
PX.Data.PXOuterException: An error occurred during processing of the field Allocated value False Inter-Branch Transactions feature is disabled
We do not pass a field called “Allocated” and not sure why the API is complaining about it.
Below is a sample request we pass and it only happens for some customers and not all:
{"CustomerID":{"value":"C006089"},"Description":{"value":"Hinnershitz"},"Details":[{"InventoryID":{"value":"DESIGNER"},"LineDescription":{"value":"Kitchen - perimeter - Hampton (Pure White), Frameless, Birch Plywood, Dovetailed Wood\n"},"OrderQty":{"value":1},"UnitPrice":{"value":7105.059800000001}},{"InventoryID":{"value":"FUEL SURCHARGE"},"OrderQty":{"value":1},"UnitPrice":{"value":355.25299000000007}}]}

You must enable Inter-Branch transactions feature.

Related

What is the "SystemTracker" in the Azure Service Bus Exception?

I am getting the below exception and would like to know what is the "SystemTracker" that is mentioned in the exception. Also, the namespace in the message entity and in the System Tracker are different. Why could those be different? One has "stage1c" and the other is "1a". If 1c is a failover for "1a", then could it log exception like this?
Azure.Messaging.ServiceBus.ServiceBusException: Put token failed. status-code: 404, status-description: The messaging entity 'sb://c0000hwabt-stage1c.servicebus.windows.net/becm.job.summary.response' could not be found. To know more visit https://aka.ms/sbResourceMgrExceptions. TrackingId:3123b33a-315a-40d5-a1e7-243b2611335e_G9, SystemTracker:c0000hwabt-stage1a.servicebus.windows.net:becm.job.summary.response, Timestamp:2022-10-20T15:56:04. (MessagingEntityNotFound)
These are set by the Service Bus service for use with correlating logs and troubleshooting from the service-side. They're helpful information to include when opening a support ticket but are otherwise not useful. Your application should treat them as opaque values and not assume any meaning to the client.

What is iKey in traces table - KQL [ Kusto Query Language] - Application Insights - Also query Optimization of following KQL query

I was getting some exceptions around 60 exceptions when I run my .NET Core Application - of a particular type - Partner center exceptions.
I have dealt with those exceptions but now I am writing some KQL queries so that I come to know if anything goes wrong beforehand.
I want to write KQL query which in future catches exceptions from partner center but not that type of exception - so how to filter them out?
My Query looks like -
traces
| where customDimensions.LogLevel == "Error"
| where operation_Name == "functionName"
| where iKey != "************"
I saw this iKey - what is it? and how can I write a desired query is what I need to know.
Also :
Could not find purchase charge for customer and "errorName":"RelationshipDoesNotExist" ----> this all comes in message and also customDimensions field
Can I extract this errorName and exclude these type of exceptions? Any way to do that?
For now I have used :
where message !contains_cs "Could not find purchase charge for customer"
but it has high compute price, so looking for an alternate to optimize the query.
iKey correspondents to the instrumentation key:
When you set up Application Insights monitoring for your web app, you create an Application Insights resource in Microsoft Azure. You open this resource in the Azure portal in order to see and analyze the telemetry collected from your app. The resource is identified by an instrumentation key (ikey). When you install the Application Insights package to monitor your app, you configure it with the instrumentation key, so that it knows where to send the telemetry.
(source)
I want to write KQL query which in future catches exceptions from partner center but not that type of exception - so how to filter them out?
Exceptions are stored in the exceptions table. You can filter them based on a known property like the exception type. For example, say you want all exceptions except those of type NullReferenceException you can do something like this:
exceptions
| where ['type'] != "System.NullReferenceException"

How can I handle exception in Azure Logic App

I'm using Azure Logic App. This is the architecture:
I have a Scope Insert Row that include an insert statement in database.
I would like to send via mail the message of the exception of the insertion.
For example if the Insert statement failed with Foreign key exception, i would like to send this message.
How can I refer to this error message inside the 'Send error Msg' feature?
Thanks a lot guys :)
You could set the Configure run after value to implement it. Set the Send an email action run after Insert row has failed.
If the Insert action success, the send mail won't execute and if it fails the send mail would work. You could also add the run after action value like the time out or is skipped, they are all kind of exceptions.
UPDATE: If this is your error message, you could add it with #{body('Insert_row')?['message']} in code view mode.
And here is my error message and the subject setting.
You can make use of Filter Array and result function to capture the actual error of an action failed in a Scope.
For more insights with example see following article - How can I handle exception in Azure Logic App
Thanks,
Maheshkumar Tiwari
TechFindings...by Maheshkumar Tiwari

ListView in sharepoint 2013

I am getting following error when I use pagination of view.
Unable to render the data. If the problem persists, contact your web
server administrator.Correlation
ID:c64a4e9d-64d2-3009-f658-7f1c8b0faebc
When I checked the Logs from ULSViewer I got these errors messages
Error while executing web part: System.ArgumentException: The
specified view is invalid. at
Microsoft.SharePoint.SPViewCollection.get_Item(Guid guid) at
Microsoft.SharePoint.ApplicationPages.InplaceViewEditor.get_View()
at
Microsoft.SharePoint.ApplicationPages.InplaceViewEditor.RenderListView()
at
Microsoft.SharePoint.ApplicationPages.InplaceViewEditor.Execute(String
strCmd) at
Microsoft.SharePoint.ApplicationPages.InplaceViewEditor.OnLoad(EventArgs
e)
Forced due to logging gap, cached # 12/24/2015 10:59:32.88, Original
Level: Verbose] No data was found on the incoming client request
Proxy response returned error: 'The remote server returned an error:
(601).'
Could you please check and let me know what is the issue? I am not able to resolve it.
Thanks in advance.
Best Regards,
Manoj.
Have you added the custom web parts or add custom code?
For troubleshooting the issue, you could check things below:
Create a new list view to check if the same issue will occur.
Do an IIS reset to check if it can work.

Padding is invalid and cannot be removed while sending push event to my application

We are using Docusign Connect to leverage the push functionality. This feature is great and we are no more worried of reaching REST call limits.
But while checking connect logs on DocuSign console- We found failure entry which is failing because of below error:
9/16/2013 6:50:23 AM Connect send to: https://myURL.com/EventListener
9/16/2013 6:50:23 AM Envelope Data (documents were included):
9/16/2013 6:50:23 AM Error: Exception in EnvelopeIntegration.RunIntegration: <EnvelopeID> :: https://myURL.com/EventListener :: Error - Exception decrypting. Padding is invalid and cannot be removed. Original Exception: Padding is invalid and cannot be removed.
Looks like this is some internal exception at Docusign. Can someone help us to resolve this issue?
This is indeed a bug on DocuSign's side. It's newly introduced which means it most likely came from the latest release. Will post an update here once resolved, thanks for your patience.
DocuSign Team

Resources