Occassionally, API call returning null for all Usr fields.

Update:

I have have two of my windows open. If I press F5 to force a requery on one screen and before it finishes, I press F5 on the other, I’ll get the erroneous query results, but only on one of the calls.

And the time for these bad result sets is very quick.

@Django 

I am currently working on a related issue. It is still under investigation, and I will probably have some findings to share in a week or two.

Thank you @RohitRattan88 - let me know if I can help in any way.

Just to add some more details. I notice that the Request Profiler indicates that the SQL Count column is a little more than double what it should be when the error happens.

@Django thank you for offer. I will reach out to you if needed

Just to add some more details. I notice that the Request Profiler indicates that the SQL Count column is a little more than double what it should be when the error happens.

 

that is interesting. thanks for pointing it out.

@Django which version are you trying with?

We had a similar issue in some 22r1 versions. 

If you are on something like 22r1 Update 15, I recommend you to upgrade to the latest 22r1 and try again.

@RohitRattan88 - yes, I noticed this. I have the Request Profiler results for a successful result and an unsuccessful result. When the issue appears, the Note table is queried by itself multiple times but when the process works the Note table is never queried by itself.  I’m going to document the differences between a good result and a bad result so that’s available.

@Dmitrii Naumov - this is version 22.213.0010

As I said, I can reproduce this at will and it is on the acumatica.com saas environment, so if I can help, I’d be happy to assist.

@Dmitrii Naumov - In our saas sandbox environment we upgraded to 22.218.023.  I’ve sends hundreds of async requests through the API over the course of a couple of minutes

100% success rate.

Thank you for the suggestion!

I did notice that the profiler indicates rows with higher SQL counts but the proper data is being returned.

@RohitRattan88 Just in case it helps your investigation, on 22.213, when I had failures, the details under the Logged SQL Count column included a high number of calls to the Note table (screenshot below). But, when I had successes - there were zero calls that only were for the Note table. (But success and failures make calls to Note,NoteDoc,SOLine, etc)

After the update to 22.218 even my high Logged SQL Count data does not include any calls that are only to the Note table.

@Django great. thanks for sharing your findings.

@Django I am having the same problem. Trying to retrieve the UDF on customer screen but udf values are still null. My build is 22.218.0023 but still not success. 22R2

Any suggestions on how and what to do to get the UDF values even it is present .
 

https://localhost/entity/Default/22.200.001/Customer?$filter=CustomerID eq '000002'&$custom=Baccount.AttributeAGDCRAN

 

@tahayabali  Can you remove the $custom=BaccountAttributeAGDCRAN from the request and replace it with:

$expand=Attributes

Just to see what comes back?

@Django It returns the Attributes but not the user define fields. The custom is empty after this call. But $custom=BaccountAttributeAGDCRAN returns custom dict but with null values

@Django and @Dmitrii Naumov any suggestions?

.