This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Hello everyone,
We have implemented a direct Fetch Attendee integration with our attendee master data in Veeva Network, which works very well. It ensures that users always retrieve the most up‑to‑date and complete attendee information directly from the source system when using the search functionality.
However, we have a concern around user behavior:
end users can still select attendees from the “Recent Attendees” list instead of triggering the search, which bypasses the fetch call to Veeva Network and may result in outdated data being reused.
We are therefore looking for ways to better control this and had a couple of questions:
So far, we have been able to remove Favorites from a user’s profile, but this only removes the favorite flag—the attendees still remain visible and selectable in the Recent Attendees list.
Any guidance or best practices would be greatly appreciated.
Thank you in advance,
Camilo
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@Kmilogon I don't believe either of those options are available. I did read something in our knowledge base about a workaround though, but I'm not sure it is something you would want to do.
Is this related to a certain attendee type? Which attendee types are being fetched?