Prepopulate Contact and Account when Creating a Case.

(1) Share

Report

Posted on by jstraumann

Hello all:

I am struggling to figure out how to pre-populate the Account and Contact when a logged on user creates a new case. It also occurred to me this seems like a security issue, if you look at the attached screens, I am logged in with a Contact Account, however in the Case Creation form, I can choose any customer and/or Contact to create a case on behalf of, this seems like a big security hole to me? IDK why it isn't a simple, OOTB feature that for a logged on Contact, when creating a case, the Account and Contact are read-only and automatically set to the logged on user?

Can anyone help?

Categories:

Power Apps portals

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi

I didn't look at the pictures yet, but Contacts respectively cannot log in. They are just "data in a table".

The issue is not that they are a contact, its what permissions were given to them as Logged in Users.

These things are different. So its not a security risk in the sense of the platform, its how you implemented it and whom is logged in and what permissions they are given :-)

Was this reply helpful? Yes No
Suggested answer

Fubar 8,491 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
The portal user can only see what you give them access to see - it appears you have created some Table Permissions with Global Read on Contact and Account, this is generally not recommended as it can create a security/privacy issue (try to limit Global to things like configuration/reference data e.g. like of categories).

One of the issues will also be that Customer is a field type that can accept both a Contact and Account record (and not all Contacts will have an Account). Several different approaches:

Use the Portal/Power Pages Management App and create Metadata records for the Create basic form and set the prepopulate and onsave the https://learn.microsoft.com/en-us/power-pages/configure/configure-basic-form-metadata#basic-form-metadata-type--attribute or

On the Web Page use Liquid (you cannot run Liquid from the Basic form directly) to obtain the the guid and primary column value of the respective values, create JavaScript variables (using Liquid) with those values in the Web Page, and then use those values to populate the Lookups with JavaScript on the basic form. The Liquid 'user' object will contain the guid (.Id) of the logged in Contact, Fullname, and parent account https://learn.microsoft.com/en-us/power-pages/configure/liquid/liquid-objects#user

Was this reply helpful? Yes No
jstraumann 39 on at

Like (0)

Report
Copy link

Link copied!

@Fubar thanks for the detailed input! Unfortunately I had tried all this already with no joy. I tried to upload Pics and the Custom JS I did, but the site blocked it, so I put the files in a Zip on my Onedrive: CaseCreateMetaData.zip

Note the Case Create form is not in it's own web page, it appears as a pop up.

Was this reply helpful? Yes No
Suggested answer

GWham 58 Moderator on at

Like (0)

Report
Copy link

Link copied!
On your form, go into it and add metadata.

Select the attribute/field in the meta data and add one for contact

Under pre-populate section, select the contact and from the dropdown logged in user.

That will populate that lookup. You can also set a value on save of the form.

Alternatively, set it with js on load if you wish .. something like...

function populateLookup(fieldSchemaName, guid, name, tableSchemaName){ $("#"+fieldSchemaName+"_name").val(name); $("#"+fieldSchemaName).val(guid); $("#"+fieldSchemaName+"_entityname").val(tableSchemaName); }); populateLookup('contact', {{user.id}}, {{user.fullname}}, 'contact)

Was this reply helpful? Yes No