Skip to main content

Posts

Power apps portal/D365 Portal: Multiselect option set in power apps portal

Multi-select option set for power apps or D365 portal * Create an attribute with a single line of text. Option set values will be saved in comma-separated in the text field created. For example: new_multiselectoption (Schema name of the attribute created.) * Use below javascript on the entity form custom javascript // JavaScript source code var multiSelectOption = $('#new_multiselectoption'); multiSelectOption.hide(); var multiselect = $('<select multiple><option value="860240000">Azure Fundamentals(AZ - 900)</option><option value="860240001">Azure AI Fundamentals(AI - 900)</option></select><option value="860240002">"Azure Data Fundamentals(DP - 900)</option></select><option value="860240003">Azure AI Fundamentals(AI - 900)</option></select><option value="860240004">Dynamics365 Fundamentals(MB - 901)</option></select>'); multis
Recent posts

PowerApps Portal/D365 Portals: Set parent account lookup on a contact lookup in portal form

Ask:  I (John) have a school(Account: Cornell University) for which John is a contact. This is OOB relation between Contact(John) and Account(Cornell University).  Upon login into the powerapps portal, the account to which John belongs should be auto-populated. Solution:  Below query will get the account details with which the user belongs. Then it can be used to set the value to the account lookup. Code Below < script type = "text/javascript" > $(document).ready( function (){ //---------------------------------------------------------------------------- //Update account lookup in course level {% fetchxml queryAccount %} <fetch version= "1.0" output-format= "xml-platform" mapping= "logical" distinct= "true" > <entity name= "account" > <attribute name= "name" /> <attribute name= "accountid" /> <link-entity name= "contact" from = "parent

Powerapps Portal/D365 portals: redirect the user to specific page if all/some mandatory contact information is not filled

Ask: Upon login to the power apps portal redirect the user to a specific page if all/some mandatory contact information is not filled. Solution:  Below is the code used to redirect from the home page to the contact page if the email of the contact record which is mandatory is not filled.  {% fetchxml query %} <fetch version= "1.0" output-format= "xml-platform" mapping= "logical" distinct= "false" > <entity name= "contact" > <attribute name= "fullname" /> <attribute name= "telephone1" /> <attribute name= "contactid" /> <order attribute= "fullname" descending= "false" /> <filter type = "and" > <condition attribute= "contactid" operator= "eq" value= " {{ user . id }} "/> <condition attribute= "emailaddress1" operator= "not-null" /&g

Power apps portal/D365 Portal: User not able to login using azure active directory, Error: Registration is disabled

Ask: Unable to login using azure active directory user in power apps portal. Getting error as  Scenario: I am contact in power apps portal and i am able to login in portal. Once i deleted my contact from CRM and try to login in portal again i am getting error as mentioned below. Solution: NO ACTION REQUIRED Once contact is deleted in CRM, the data will be synced in azure AD and you will automatically able to login in portal after some time (around 30 minutes) without performing any action. * Invalid sign in attempt  * Registration is disabled

Power apps portal/ D365 Portal: How to hide the profile page in the portal

Ask : How to disable profile page in power apps portal or MS D365 portal. Solution Design : This can be achieved using a site setting which by default is true and can be changed to false. It will stop redirecting the user to the profile page when the user gets logged in. Screenshot FYR below :

Power apps portal/ D365 Portal: Set logged in portal user to a lookup .

 Ask: Set logged in portal user to a lookup. Scenario: On a portal form we have a contact lookup with the name educator. On load of the form, the value of the educator look shall be set as the logged-in user. How to do it: Click on F12 on the portal form to navigate to the designer page. There will be 3 ids available on the form. These Ids will be used to set the display name, record guid, and entity name. Implementation: Below code will be used on the entity form the custom javascript section. JS Code: $(document).ready( function (){ $( "#new_educator_name" ).attr( "value" , '{{user.fullname}}' );//Display Name $( "#new_educator" ).attr( "value" , '{{user.id}}' );//Contact Id $( "#new_educator_entityname" ).attr( "value" , "contact" );//Name of entity lookup });