Skip to main content
Solved

Client Warnings are not supported for Entity

  • March 6, 2025
  • 5 replies
  • 99 views

Forum|alt.badge.img+3

Our company recently upgraded from Apps 10 to Cloud, and in Apps 10 we had a custom LU called Ecommerce which was added as a custom tab on the Part page. When trying to add this custom tab in Cloud, the data is populating but I can not edit any data in the custom tab. I’m getting the following error:

“Client Warnings are not supported for CREATE, UPDATE, DELETE operations in [Ecommerce] entity. So 'X-IFS-Accept-Warnings' request header cannot be set to 'true'.”

Is there a way to enable client warnings for this entity, or another way to get around this error message?

 

Best answer by JHowes

The problem has been solved - I discovered I was using a Group for the custom tab when I should have been using a Singleton because I needed a 1-1 relationship between the page and the custom tab. 

5 replies

ZTC ZTC JGOTA
Hero (Customer)
Forum|alt.badge.img+14
  • Hero (Customer)
  • March 7, 2025

@JHowes  Are you able to get into IFS Studio Developer? and find the page.


wahelk
Hero (Former Employee)
Forum|alt.badge.img+11
  • Hero (Former Employee)
  • March 10, 2025

in your projection configuraion, have you allowed these operations?

 

Best Regards,

Wasana


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Customer)
  • March 10, 2025

in your projection configuraion, have you allowed these operations?

 

Best Regards,

Wasana

@wahelk  Yes I have alowed the Read, Create, Update, and Delete operations in the projection configuration for the Ecommerce tab.

 


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Customer)
  • March 10, 2025

@JHowes  Are you able to get into IFS Studio Developer? and find the page.

@ZTC ZTC JGOTA I use a tool Pl/SQL Developer for code modifications. Would the IFS Developer Studio provide additional data that is not available through the PL/SQL developer?

 


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Customer)
  • Answer
  • March 12, 2025

The problem has been solved - I discovered I was using a Group for the custom tab when I should have been using a Singleton because I needed a 1-1 relationship between the page and the custom tab.