400.1 Bad request content

When requesting the access profile Oracle ERP PRD - Contabilidade “GL” Manager or Oracle ERP PRD - Contabilidade “GL”, they are not moving to the approval flow phase and as soon as it is requested the error below is displayed on the screen:

Hi @kaiolima,

Could you remove the inverted commas in the Access Profile Name and try again please?

Thanks, I’ll test it and come back with the update.

Even after removing the quotation marks, the error persists, and we also tried to recreate

I have been able to duplicate this. Steps:

  1. Create an Access Profile with quotation marks in the name field. Mark the access profile as requestable.
  2. Go to Request Center and request the Access Profile for a user. I receive the email that the request was submitted but if I go to “View My Requests” I have the same error. The process did not proceed to approval.

I went back to the Access Profile configuration and removed the quotes from the name. I was able to confirm with the API that the name value changed and it displayed correctly. I made another request and get the same error. I disabled and enabled the Access Profile with the same result. I also made the Access Profile not requestable and then made it requestable; this produced the same result. I tried submitting an Access Request through the API using the Access Profile number and the error is the same.

The only thing that worked was to create a new Access Profile. I did find an article under support that said that standard characters except + should be OK in object names.

It looks like something is being cached and not getting the name change. @tyler_mairose @colin_mckibben @colin_mckibben - Is there a way to find out if something is wrong with this service or if this is a bug? I am thinking it is a bug because my url that is coming up has the same ending but not the same server as @kaiolima.

Alicia

@kaiolima

Try your request again on your access profile that you renamed. I tried mine again this morning and found that it is working now. I wonder if something has cleared now.

Alicia

This problem is actually still ongoing, I have now carried out the following tests:

  • I removed the approval and requested access for myself, it still persisted.
  • I tested in an anonymous tab, the error still persisted.