When a form displays a business process flow control in the header, additional controls gets added for each attribute that is been displayed in that BPF.
These controls hold unique names like: header_process_<attribute name>.
Code compare Tool: Beyond Compare with License Key
Beyond Compare
V 4.2.2
--- BEGIN LICENSE KEY ---
H1bJTd2SauPv5Garuaq0Ig43uqq5NJOEw94wxdZTpU-pFB9GmyPk677gJ
vC1Ro6sbAvKR4pVwtxdCfuoZDb6hJ5bVQKqlfihJfSYZt-xVrVU27+0Ja
hFbqTmYskatMTgPyjvv99CF2Te8ec+Ys2SPxyZAF0YwOCNOWmsyqN5y9t
q2Kw2pjoiDs5gIH-uw5U49JzOB6otS7kThBJE-H9A76u4uUvR8DKb+VcB
rWu5qSJGEnbsXNfJdq5L2D8QgRdV-sXHp2A-7j1X2n4WIISvU1V9koIyS
NisHFBTcWJS0sC5BTFwrtfLEE9lEwz2bxHQpWJiu12ZeKpi+7oUSqebX+
--- END LICENSE KEY -----
The above license key only applies to version 4.2.2.
How to filter Option Set Field options based on form
How to filter Option Set Field options based on form
In some scenarios, we may need to filter the option set types of fields' options based on some conditions.
Capture user's signature in Dynamics 365 CE
Sometimes we may need to capture user's signature in Dynamics 365.
How to exceed 50 characters maximum label length limitation to set a long label for the Dynamics 365 CE fields.
How to exceed 50 characters maximum label length limitation to set a long label for the Dynamics 365 CE fields.
As we know there is a 50 characters maximum length limitation for the fields(columns) labels of entities(tables) in Dynamics 365 CE.
Sometimes, we may need a longer label than 50 characters. How to do that?
Newly introduced client script methods for D365 CE
https://nebulaaitsolutions.com/newly-introduced-client-script-methods-for-d365-ce/
Newly introduced client script methods for D365 CE
This blog will talk about the new client script methods that can enhance UI/UX experience.
addOption
This method adds an option to your choice/choices control.
formContext.getControl(arg).addOption(option, index);Example
removeOption
Removes an option from a choice/choices control.
formContext.getControl(arg).removeOption(value);Example
clearOptions
Clears all options from a choice/choices control.
formContext.getControl(arg).clearOptions();Example
setFocus
Sets the focus on the control.
formContext.getControl(arg).setFocus();Example
setLabel
Sets the label of the control.
formContext.getControl(arg).setLabel(label);Example
addOnLookupTagClick
Adds an event handler to the OnLookupTagClick event.
OnLookupTagClick:- This event occurs when the user clicks the tag in a lookup control.
formContext.getControl(arg).addOnLookupTagClick(myFunction);createPane
Provides all the information to create side panes.
Xrm.App.sidePanes.createPane(paneOptions);Click here to learn more about paneOptions
Example for addOnLookupTagClick & createPane
Creating HTML Web Resource To Show Image Attached In Notes Using Web API
https://www.c-sharpcorner.com/article/creating-html-web-resource-to-show-image-attached-in-notes-using-web-api/
Show or hide the 'Add New' button on form sub-grid based on the value on the form
https://ribbonworkbench.uservoice.com/knowledgebase/articles/489288-show-or-hide-the-add-new-button-on-form-sub-grid
How do I show or hide the 'Add New' button on form sub-grid based on the value on the form.
You cannot use the ValueRule because the context of this rule must be run from a form Command Bar - so we must use a custom JavaScript rule.
Solution:
1. Create a JavaScript webresource that contains the function:
function ClientHooks_Ribbon_OpportunityRibbon_SubGridEnableRule() {
var attribute = Xrm.Page.getAttribute('<your attribute logical name here>');
return attribute.getValue() != null; // Return true to enable the button
}This function will be used to enable the sub-grid add button when there is a value in the attribute you reference.
2. Add the child entity that you want to change the sub-grid behaviour for to a solution. Also add the webresource with the javascript function above and then load the solution into the Ribbon Workbench.
2. Select the child entity from the Entities panel and identify which button you need to customise:]
3. Right-Click on the button and click Customize Command
4. The new command will show in the Solution Elements Panel and additionally all the referenced EnableRules and DisplayRules will also be added. Since we don’t need to customise these, we can select each one in turn and set IsCore=True in the properties panel.
5. Now to add the new ValueRule. Right click on the new customised command and click Edit Enable Rules.
6. Click Add New and then Add Step. Select Custom Javascript Rule and set the properties:
· FunctionName = ClientHooks_Ribbon_OpportunityRibbon_SubGridEnableRule
· Library = <Select the library you added above>
7. Click Publish
Refreshing the subgrid command bar
You will find that when the form is loaded, if there is a value in the attribute you have referenced in your enable rule, the Add New button will be visible. If however the value changes, the sub-grid command bar will not automatically refresh to reflect the new state. Upon adding or deleting rows in the sub-grid the command bar is refresh – but this isn’t much use in this case.
The main form command bar can be refreshed using Xrm.Page.ui.refreshRibbon() however this will not refresh sub-grid command bars. Instead, we can add an onchange event to the fields that are used in our VaueRule and call:
Xrm.Page.data.save();
This will refresh the sub-grids and re-evaluate any of the EnableRules however it will also save any other dirty attributes and so should be used with caution if you do not have auto-save enabled.
[Demo - Step by step] Power Pages & SharePoint File Upload
Just show the different parts from the previous demo which was finished by using Power Apps Portal.
[Demo step by step] Power Apps Portal & SharePoint File Upload
Demo step by step:
Power Apps Portal with several steps of process flow by using Advanced Form (Web Form)
Support SharePoint Documents upload.
Power Apps Portal issue: "Server Error in '/' Application
Power Apps Portal "Server Error in '/' Application
"a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"
The below solution could be a reference for you.
1. Go to portal app setting:
2. Go admin page:
3. Try "Update Dynamics 365 URL" firstly, if still doesn't work.
Then try "Restart Portal". After several minutes, the portal may recover.
Hide "New folder" button of SharePoint in Power Apps Portal
When integrated SharePoint to Portal, there will be two buttons for document management: "Add files" and "New folder".
If you don't hope the user to be able to create new folders, you may follow below steps to hide "New folder" button.
1. Find the specific Entity form your Share Point document upload grid located at within your Portal Management.
2. Switch to "Additional settings" tab.
3. Go to the "Custom JavaScript" section part, then type the following JavaScript code:
$(document).ready(function(){
$('a.add-folder.btn.btn-info.action').hide()
})
4. Go to your Portal Designer, click "Sync Configuration"-> "Browse website" button, then launch your Entity form again, the "New Folder" button would disappear:
Power Apps Portal : How to add Advanced Form / Web Form into webpage
Power Apps Portal : How to add Advanced Form / Web Form into webpage
Precondition: An advanced form(web form) and a basic form (entity form) have been created.
Step 1: Add a basic form (entity form) into a section of the webpage.
Step 2: Update the script:
Change "entityform" to "webform"
Change the form name to the advanced form's name
Step 3: Browse website
Power Apps Portal - Entity Form / Basic Form Doesn't show in the published webpage
Issue: Power Apps Portal - Entity Form / Basic Form Doesn't show in the published webpage
Reason: Form doesn't support the current webpage template.
Solution: Change the webpage template.
Conditionally Show/Hide fields on Power Apps Portal by Using JavaScript
$(document).ready(function () {
$("#prag_manufacturer").change(onDisplaySectionChange); onDisplaySectionChange(); }); function onDisplaySectionChange() { var varManuf = $('#prag_manufacturer').find("option:selected").text(); if (varManuf === "Other") { $('#prag_othermanufacturer').parent().parent().show(); } else { $('#prag_othermanufacturer').parent().parent().hide(); } }
Subscribe to:
Posts (Atom)