Hi,
We have a custom table in our instance for 'favorite' financial account records (for a very complicated account structure). We have created a form in our portal which allows users to inactivate, activate, and create new favorites. This all works, but the form also will create a case each time an end user updates their favorites. We don't need a case or request created. The only data the authenticated user has access to is their own favorites and we don't need to track their changes. I've thought that perhaps I can use UI Builder to create the interface where the end user can modify their favorites, but this so far has been very complicated. Does anyone have any suggestions on the best way to create this user interface within our portal?
Thanks,
Karen
