Answered

Portal user creates contacts

(1) Share

Report

Posted on by Clerc

Hi,

I want to build a user portal to allow authenticated users to create their own work assignments and associate them with contacts. What are pros and cons about allowing those users to create and manage their contacts in the standard Contact table? I plan to use Contact Access permissions to limit their access only to the Contacts they created.

James

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Michael E. Gernaey 53,504 Super User 2025 Season 2 on at

Like (1)

Report

Hi

Its a really way too open ended question. We have no idea what they plan to do with those contacts. Heck I dont even know that I agree you are using the OOB Contact Table

Are these actually people, or are they Customers? Are they Organizations or Companies? Can it be all of them? Will the have access to the Contact and Account table?

etc etc..

Doing this more than 40 years and its just not enough info to give you a true answer, everything else is a pure guess.

Was this reply helpful? Yes No
Clerc on at

Like (1)

Report

@FLMike,

Edited 25 Jul 2024 at 20:24:01

Fair enough. My targeted customers are 1099 contractors accepting short-term contracts from businesses in this area, and duration are 2 hours to a few days each job. The user portal will have the fields they will need for most jobs, unlike any major calendars. I plan to add Requestor Name and Bill to columns in each contract record. Bill to would come from Account table and Requestor Name from Contact Table.

I created a custom contact table just for those portal users with all rows' view set to Contact access. They can see only the accounts and contacts they created. The problem I ran into is the primary name column in the custom Contact table does not offer Fx formula to put First Name and Last Name columns together. Selected contact from a lookup contact form returns the primary column value which is set to autonumber.

I also tested the system Contact table to see if portal users could create and maintain their own contacts in the table with lists and forms set to Account or Contact Access. The primary column is Full Name, which is a system name, and returns the full name from lookup dropdown list. This fits our business requirement. This lead me to the original question.

Actually, I have two questions. How do I parse Full Name to the primary column in the custom contact table? If I cannot, what are pros and cons of allowing portal users create their own contacts in the system Contact table?

Was this reply helpful? Yes No
ankit_singhal 590 Super User 2025 Season 2 on at

Like (1)

Report

When a contact record is created in dataverse then wonder will be system or portal admin user which you are created so it will be difficult to restrict the user to access their record only. you can write logic when contact is create then it will assign to the respective user and give user level access.

Was this reply helpful? Yes No
Verified answer

Fubar 8,384 Super User 2025 Season 2 on at

Like (1)

Report

Its important to clarify what 'Portal' you are using.

If Power Pages, note, there is a Power Pages forum that would be the more appropriate place to post. If Power Pages then restricting access can be relatively simple or complex depending on your needs. If Power Pages, then would generally use the out of the box Contact table, in its simplest form you can user Table Permissions with scope = Contact, and when the portal user creates records set the form to save the Current Portal user into Contact lookup on the form (or set it via a form Metadata record). Similar can be done with Accounts e.g. users can access data of other Contacts belonging to the same account).

It can get a lot more complex when you start to get into using Table Permissions with scope = Parent or you have requirements that will lead to conflicting Table Permissions.

Was this reply helpful? Yes No