 |
I see, i think what you need to do is to remove the View permission of the portal user on the object in question. Then you need to enable the view permission of the relationship between the portal user and the object. You should see this both in the permission settings.
For the trigger, i dont think that there is currently a better way to do this.
Hope this helps.
In grid controls you should be able to set a specific view to use for each lookup field in the grid.
For me, to be able to do "I have a grid component on a Portal page and would like to filter the records to only show records for the specific Portal user." I would create new views specifically for your portal (no permissions to anyone except portal users) and set a filter Portal User object == CURR_VISIT per view.
This way all records that are seen in the lookup should belong to the currently logged in portal user.
As for record creation where you need them to be able to create records for themselves, don't include the Portal User field in the grid due to the obvious drawbacks and problems. What I would do in this case is to create a trigger on your Grid's object where during after create if a record is being created from the portal (rbv_api.isPortal() == true) I would automatically assign the Portal User relationship with the currently logged in portal visitor {!#CURR_VISIT.id}
I'm not 100% sure about the token's validity but the description should give you an idea on its implementation.
Hope this helps.
|
|
I see, i think what you need to do is to remove the View permission of the portal user on the object in question. Then you need to enable the view permission of the relationship between the portal user and the object. You should see this both in the permission settings.
For the trigger, i dont think that there is currently a better way to do this.
Hope this helps.
|
|