BTP Abap Environment additionalBinding metadata cache

[#1]

Hi Experts,

I'm developing a Fiori Elements app using RAP in the SAP BTP ABAP environment. This application includes Value Helps with additionalBinding. However, I have noticed that sometimes changes to the additionalBinding for a Value Help are not reflected on the frontend.

Upon investigation, I discovered that these Value Helps, which are based on other CDS Views, make a metadata call the first time they are invoked on the frontend.

This metadata, separate from the main Fiori Elements metadata, contains the additionalBinding as a Value Help input parameter. Unfortunately, it does not update according to the changes made in the CDS.

Eventually, the metadata updates after modifying the metadata extension object in other places. This issue is difficult to consistently replicate.

I suspect this might be a caching problem on the backend. In an on-premise system, we could clear the backend cache directly by running a report. However, in BTP, there seems to be no straightforward way to do this. How can I check if the cache is the problem, and how can I invalidate it to update this metadata on the frontend?

Thanks!