Request for assistance on APIs - Restriction Group by Subaccount and Reverse Journal Transaction

Hi @vidyakeerthik,

For the 1st question,

• I don’t think it is possible to create Restriction Group from the Restriction Groups by Subaccount(GL104030) screen. To create Subaccount group you can use GL Account Access(GL104000) screen. For more information on adding subaccount group refer to the following documentations,
  • https://help.acumatica.com/(W(6))/Help?ScreenId=ShowWiki&pageid=4b15211e-d9bb-4fb9-943f-85c735fce9c3
  • https://help.acumatica.com/(W(6))/Help?ScreenId=ShowWiki&pageid=51b5ba54-d95d-4099-b55c-c631acbb67fe

From the Restriction Groups by Subaccount(GL104030) screen, you can enable or disable the Included checkbox in the grid. To do that, map the GL104030 and its detail entity like in below screenshot,

Do a GET request with expand, like

GET: <<Instance URL>>/entity/DefaultExt/23.200.001/RestrictionGroupsSubAcct/000000?$expand=RestrictionGroup

Now do PUT request using ID(like below) to update the Included value, 

Put: <<Instance URL>>/entity/DefaultExt/23.200.001/RestrictionGroupsSubAcct

{
    "id": "f29cb555-4129-44dd-9565-075eb0733e62",
    "RestrictionGroup": [
        {
            "id": "c5544f14-8e0b-4127-ba40-0a84413ff8f1",
            "Included": {
                "value": true
            }
        }
    ]
}

Feel free to post if you have any questions.!

Hi @vidyakeerthik,

For the 2nd question,

When you invoke Reverse action from UI, you can notice there is a pop-up warning message(think depends on the transaction you are reversing) and upon user confirmation the system creates a new GL but doesn’t save it. So the new Journal Transaction created will simply be <NEW> unless you save it manually.

There could be the two possible reasons, why the reversed transactions isn’t saved when invoked from API.

It might be tricky, but to be able to do it from API you might have to customize to ideally bypass the pop-up message and persist the new transaction that is being created. Hope that helps, Good Luck.!

Hi Vignesh,

Thanks for your review and detailed inputs.

#2 yes, we understood and its working now.

#1, we tried the same way like first to get id and the use that id in the put call, to udpate Restriction groups, no luck.

Same behaviour like, we don’t see any error, status is 200 but selected groups are not reflecting in the instance screen.

Below are the screenshots sharing for your reference.

Hi @vidyakeerthik,

Request seems good to me. Can you please share screenshot of the Endpoint extension and the field mapping of the Restriction Group?

Other, possible reason could be that you are passing the wrong ID in the PUT request. Kindly test and confirm if you are using the right IDs. Thanks

Hi Vignesh,

Thank you for your response. I've attached additional screenshots as per your request.

Could you please review and provide your Inputs.

Note: A custom endpoint has been created for the restriction group by Subaccount (GL104030) i.e RestrictionGroupBySubaccount

Requirement : The requirement involves updating groups for a specific subaccount. The API allows selection of group names and saving them by passing the Subaccount ID and the Group name through Postman.

Looking forward to your feedback.

 

As we have mentioned in above screenshots ,  WID-000 Subaccount ID  putted request Included true for Cash Account Access

Adding the Endpoint Screenshot
 

Thanks & Regards,
Aditya D

Hi Vignesh,

Did you get a chance to look into the inputs shared by Aditya.

Any further suggestion please

Thanks & Regards,

Vidyakeerthi K

Sure Vignesh,

Thank you so much for your review and inputs on this request.

Will create a case and coordinate further.