ETag & Persistent table BDL RAP Part 17

[@Momo-jl6ii]

Your dedication and commitment is commendable ! Outstanding as usual.

[@SAPTECHNOMANIAC]

Thank you so much 😀

[@rajeshkura6452]

Thank you Ram Wow.. E-tag concept is like a magic

[@SAPTECHNOMANIAC]

You're Welcome 🙂

[@vivekb8297]

Hi Ram, I followed your example closely for implementing F4 help, but I'm facing a problem. After selecting a value from the F4 help, it is not being populated into the corresponding field. Could you please help me figure out what I might be missing?

[@vivekb8297]

I used the interface view I_CurrencyStdVH instead of I_Currency, and it worked

[@SAPTECHNOMANIAC]

Some time there is an issue you can create ur own F4 help or directly consume table

[@lochovuuc7552]

Hello RAM, thanks for your sharing, I followed your instructions but had a problem, when creating and editing my TravelID and BookingID I couldn't import them, can you give me some advice?

[@SAPTECHNOMANIAC]

Can you check code which I put on github (available in channel heading) and Try to use latest version of eclipse .

[@gabrielstein335]

Thanks again for your Videos, it is very helpful.

[@SAPTECHNOMANIAC]

You are welcome!

[@nikeshsingh3065]

For ETag, if we are creating an unmanaged scenario, and if we don't have the LastChangedAt field in the underlying standard SAP database table then how to handle the Etag?

[@SAPTECHNOMANIAC]

We have to update some fields in the custom table that can work as an ETag each time we do any update operation we should update and validate

[@nikeshsingh3065]

@@SAPTECHNOMANIAC What about a standard table? If my BO CDS are built on the standard table and that table does not have LastChangedAt, how can ETag be handled?

[@devendrapatel6389]

Which is better Optimistic concurrency control or Pessimistic concurrency control ?

[@SAPTECHNOMANIAC]

The choice between Optimistic Concurrency Control (OCC) and Pessimistic Concurrency Control (PCC) depends on system requirements, workload patterns, and the likelihood of conflicts. Optimistic Concurrency Control (OCC) OCC assumes conflicts are rare, allowing transactions to execute without locks. Conflicts are detected at the commit stage (e.g., version checks). It’s ideal for read-heavy systems with minimal contention, as it avoids locking overhead, making it scalable and high-performing. However, it requires retrying transactions in case of conflicts, which can increase response times. OCC is best for applications prioritizing user responsiveness, like analytics dashboards or collaborative apps. Pessimistic Concurrency Control (PCC) PCC assumes conflicts are common and locks resources upfront to prevent them. It ensures data consistency and avoids anomalies, making it suitable for write-heavy systems with frequent updates or scenarios needing strict consistency (e.g., banking systems). However, it introduces locking overhead, risks deadlocks, and reduces concurrency, which may impact performance in read-heavy environments.

[@saikatnath]

Thank you @SAPTECHNOMANIAC for sharing this video. I've been eagerly anticipating its upload.😊😊

[@SAPTECHNOMANIAC]

Hope you enjoyed it!

[@saikatnath]

@@SAPTECHNOMANIAC yes i did !

[@sonukumar-yj3gc]

is it mandatory to include "last_changed_at" kind of field as part of table to apply eTag?

[@SAPTECHNOMANIAC]

Yes it is it have unique value each time during CUD

[@sunilkb2849]

Ram Nivas bhai, good to see your content. Hope you remember me... Good luck! Keep educating...

[@SAPTECHNOMANIAC]

Yes bro, Thank you 🙂

[@sibatsyasahoo8289]

My create not working, travel grid out help me to fix this

[@SAPTECHNOMANIAC]

Please check your code:- github.com/ramniwas04/SAP-TECHNOMANIAC-ALL-CODE/tree/main/Final%20Managed%20APP%20Backup

[@metrickz1280]

thank you for video but is it not possible that you buy a better microphone ?

[@SAPTECHNOMANIAC]

You suggest some good microphone as of now I am using boya ...

[@yury3484]

Hello Ram! what means "lock master" command?

[@SAPTECHNOMANIAC]

kzbin.info/www/bejne/r36nmouprNBkZ9k

[@aakashgt3440]

Hi ram, i'm getting blank fields for agency id and customer id alone how can i rectify this issue

[@aakashgt3440]

issue is sorted out this happen due to spelling mistake value help definition -> additional binding-> element name

[@SAPTECHNOMANIAC]

👍

[@vivekb8297]

Thanks!

[@SAPTECHNOMANIAC]

Welcome!

[@ebrahimmujawar3112]

Hi I am creating same rap app but for create operation my travel field is disabled. Same goes for booking id field.

[@SAPTECHNOMANIAC]

Did you use readonly on create travel? If yes than you have to write early or late numbering method to fill travel.

[@selvamanii6834]

@@SAPTECHNOMANIAC Hi Ram, i am also getting the same issue, but your program is working without doing write only or late numbering( till 12:01 ) how?

[@SAPTECHNOMANIAC]

@@selvamanii6834 Not sure why you are getting this issue. Make sure you are using latest version of ADT

[@XXX-z4x7n]

in behavior u can check that, for travel entities u need to change -> field (readonly:update) TravelID so that u can create a new Travel ID. If you cant that in behavior it can be -> field (readonly) TravelID

[@have_nice_tiem]

@@XXX-z4x7n hi, im facing same issue, tried field ( readonly ) TravelId; also tried field ( readonly:update ) TravelId; none worked..