Hi, thank you for your videos! They are great and very helpful. I have similar scenario and I created two bindings - for OData V2 and V4. Do you know why the errors appears in popup only when the Fiori app uses V2? For V4 I can see the errors in console but they don't show up. Thank you very much!
Hi @madaf007 there might be some changes to this functionality and updates. Please visit below video recorded few days back and may help you Part 12: Unmanaged ABAP RESTful Application Programming Model (RAP) - Validations ua-cam.com/video/Jqz3uhW5rYE/v-deo.html Please consider subscribing and sharing my channel with your friends and colleagues if you like 👍 and help grow
@@codeinmins Thank you for quick response! I checked the video. I implemented error handling in finalize and check_before_save methods and unfortunately still the same. It looks like sapui5 (1.120.x version) doesn't trigger message popup for OData V4 when the errors comes from batch in status 200 (single process in batch returns 400). But I cannot find similar issue on the internet so maybe I did something wrong.
Hello, I've done your examples on my side and everything worked fine in OData V2 and V4 so I started looking in my case more deeply the reason. And probably the reason was the Timestamp in the key of Interface View. Without it everything worked as expected. Thank you once again for your videos!
@codeinmins now I'm facing with refreshing the line with OData V4. When I use OData V2 in your scenario, after executing action "Update Status", the row in the list is refreshed automatically and Status is changed on frontend. Using OData V4 not. Do you know maybe how it can be handled? Edit: Ok, Side Effects are needed :) In my case they should be done via annotation.xml because of old version of system and I cannot do it inside Behaviour
It just weirds me out a little that this kind of behavior setting is under @UI annotation, instead of maybe something within the action definition in BDEF. After all, this annotation by itself doesn't convert the list report into a multi-select. But anyway, I'm glad I came across your content, it is helping a lot! Thank you very much!
Hi Rodrigo Oliveira, thanks for visiting my channel and glad they are helpful to you. In RAP most of UI annotations needs to be added in fiori app RAP is not supporting currently… Please consider subscribing and sharing my videos and channel with your friends and colleagues and help grow if you like…
Hello! But why can't we check data in CHANGE_SET? We retrieve all keys, select data, perform LOOP and check data. In case of error skip line, else -> update. what is the difference?
Change set executes in same session but isolation as name suggest it executes in separate sessions and that’s why you get error messages for each failed record and you are also able to update correct records… hope this helps…
Hi, thank you for your videos! They are great and very helpful. I have similar scenario and I created two bindings - for OData V2 and V4. Do you know why the errors appears in popup only when the Fiori app uses V2? For V4 I can see the errors in console but they don't show up. Thank you very much!
Hi @madaf007 there might be some changes to this functionality and updates. Please visit below video recorded few days back and may help you
Part 12: Unmanaged ABAP RESTful Application Programming Model (RAP) - Validations
ua-cam.com/video/Jqz3uhW5rYE/v-deo.html
Please consider subscribing and sharing my channel with your friends and colleagues if you like 👍 and help grow
@@codeinmins Thank you for quick response! I checked the video. I implemented error handling in finalize and check_before_save methods and unfortunately still the same. It looks like sapui5 (1.120.x version) doesn't trigger message popup for OData V4 when the errors comes from batch in status 200 (single process in batch returns 400). But I cannot find similar issue on the internet so maybe I did something wrong.
Hello, I've done your examples on my side and everything worked fine in OData V2 and V4 so I started looking in my case more deeply the reason. And probably the reason was the Timestamp in the key of Interface View. Without it everything worked as expected. Thank you once again for your videos!
@codeinmins now I'm facing with refreshing the line with OData V4. When I use OData V2 in your scenario, after executing action "Update Status", the row in the list is refreshed automatically and Status is changed on frontend. Using OData V4 not. Do you know maybe how it can be handled?
Edit: Ok, Side Effects are needed :) In my case they should be done via annotation.xml because of old version of system and I cannot do it inside Behaviour
It just weirds me out a little that this kind of behavior setting is under @UI annotation, instead of maybe something within the action definition in BDEF. After all, this annotation by itself doesn't convert the list report into a multi-select. But anyway, I'm glad I came across your content, it is helping a lot! Thank you very much!
Hi Rodrigo Oliveira, thanks for visiting my channel and glad they are helpful to you. In RAP most of UI annotations needs to be added in fiori app RAP is not supporting currently… Please consider subscribing and sharing my videos and channel with your friends and colleagues and help grow if you like…
Hello!
But why can't we check data in CHANGE_SET? We retrieve all keys, select data, perform LOOP and check data. In case of error skip line, else -> update.
what is the difference?
Change set executes in same session but isolation as name suggest it executes in separate sessions and that’s why you get error messages for each failed record and you are also able to update correct records… hope this helps…
@@codeinmins Thank you for this explanation, I was also having the same doubt.