Monday, June 13, 2022
2 changes · master
Resolved issues and error corrections
Event organizers can now search registration records by the answers attendees selected or typed in event questions. This makes it easier to group, find, and organize attendees based on their responses.
Original PR description
Since: a0092d0011ec62de62e46dfa57cd16ff83bd7201
Users can see attendees' selected answers in the registrations list view using
an optional field ("registration_answer_ids").
However, searching on this field is currently not correctly supported as the
"event.registration.answer" model does not implement it (no "_rec_name" and no
"_rec_names_search").
This commit adds a "_rec_names_search" attribute to allow users to search on
both "value_answer_id" and "value_text_box" fields.
This makes it easy to search for all attendees that have filled in a specific
answer, allowing a better organization of the event based on question results.
Task-2868203Documents spreadsheets now use a dedicated loading error instead of the text "Loading..." while data is still being fetched. This prevents unfinished data from being treated as a real formula value and improves reliability when fetches fail or are retried.
Original PR description
[REF] documents_spreadsheet: throw custom loading error Currently, formulas which are loading some date return the string "Loading..." This can lead to weird situations where the string is the input to another formula which understands it as a valid input and could potentially be used as an unexpected RPC argument. Task 2880112 Co-authored-by: Rémi Rahir <rar@odoo.com>