on 2023 Feb 07 2:17 PM
Hi,
I have a Fiori Elements app for Object with List/Object page. The oData version is 4. I implemented a custom view as is described here.
In the custom section, I have a custom calendar control that displays the same objects as are shown in the table. The problem I am seeing is with refresh. Neither Save Draft nor Discard Draft triggers refresh of my custom view. Hence the calendar keeps showing obsolete data. Is there a suitable extension point that I could use to force refresh of my custom control? The global side effects described for draft do not seem to work in this case. I can't find any suitable extension point in the documentation for oData v4.
Thanks
Request clarification before answering.
Hello, maybe you could implement an event handler on extension API for Object pages, specifically AfterActivate and AfterCancel, and call an OData refresh method so your component is up-to date with changes.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
thanks for your comment but the extension point is only available for oData v2. I have service with version oData v4. On the side note, it's really annoying that we have two versions of the same concept and each version works slightly differently.
Anyway, today I found a similar workaround. I use override for method routing.onAfterBinding. So when binding changes, I remember if binding is for draft or not. When binding changes next time and it was a draft previously, I refresh my bindings. It seems to be working fine.
User | Count |
---|---|
64 | |
8 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.