You may utilize Entity Permissions if you wish to secure records, but if you want to simply provide a filter as part of the set of filter options that is relevant to the current portal user, the Entity List feature supports filtering of current user, user's parent account, and/or website at any depth. Simply build the view filter in CRM to match any single contact record and the code will replace it's value with the actual value at runtime. No need to assign values to fields on the Filter Conditions section.

  • The control will find all condition elements where uitype="contact" and set the value to the actual value of the current portal user's contact ID.
  • The control will find all condition elements where uitype="account" and set the value to the actual value of the current portal user's parent account ID.
  • The control will find all condition elements where uitype="adx_website" and set the value to the actual value of the current website ID.
Example View Filter Criteria

The following image shows an arbitrary contact assigned to a filter condition, this contact happens to be a stub 'dummy' contact but this could be any contact record. The ID of this record will be replaced by the actual value of the ID of the user viewing the page. If the user is not logged in then no records will be returned. This provides greater flexibility in filtering the data based on the user and website contextually.

If you are filtering by current portal user's contact or parent account then it is recommended that you associate a Web Page Access Control Rule to the Web Page to force the user to sign in. You would create a Web Role with "Authenticated Users Role" checked. Create a Web Page Access Control Rule with "Restrict Read" right and associate the Web Role. This will force users to be signed in to view the page and therefore allow the data to be filled accordingly.

Filter Criteria