PnP WatchParty for Microsoft's 'LearnTogether Building apps with Microsoft Graph' event

by Contributed | Apr 7, 2021 | Technology

This article is contributed. See the original author and article here.

Configuring On-Premise data gateway with new user in Azure AD tenant

by Contributed | Apr 7, 2021 | Technology

This article is contributed. See the original author and article here.

Issue: Unable to configure and use On-Premise data gateway when user is having personal account (*.gmail.com/*.yahoo.com etc) or work/school account belongs to multiple tenants by design.

Workaround:   We can follow the below steps to install, configure and create on-premise data gateway on on-premise as well as on Azure with below steps. 

Creating user in Azure AD tenant:

• Create new user in the destined Azure Active directory. You can refer this doc CreateNewUser .


• Provide contributor access at subscription or Resource Group (where you want to create the Azure data gateway) level


• Sign-out from the portal and sign-in with new user created above . It will ask you to change password, update the password and check if you are able to login to portal.

Install  and Configure On-Premise data gateway on On-Premise machine:

• Now, you can download and install the on-premise data gateway on your On-Premise machine. You can refer to the link for downloading and installing gateway logic-apps-gateway-install .


• Once the gateway is successfully installed, it pops up for the sign-in to configure the gateway.


• Use the new user created in the Azure Active directory to sign-in and configure gateway. Follow the steps mentioned n above link. install-data-gateway 

Verify Gateway Cluster in Power Platform center:

•  You can verify whether the gateway clustered configured is available in the power platform portal (log in with new Azure AD user) Manage DataGateways.


• You need to select region in which you configured gateway in portal, option is available on the top right side.

Creating On-Premise data gateway in Azure:

•  Sign-in to azure portal with new Azure AD user used to configure the data gateway on on-premise machine


• Create new Azure On-Premise data gateway resource in respective resource group where user has access. you can follow this doc on how to create azure On-premise data gateway resource. Create-azure-gateway-resource 

Note:

• This can be an extra effort for managing the new user we created in Azure AD tenant.

Cumulative Update #10 for SQL Server 2019 RTM

by Contributed | Apr 6, 2021 | Technology

This article is contributed. See the original author and article here.

The 10th cumulative update release for SQL Server 2019 RTM is now available for download at the Microsoft Downloads site. Please note that registration is no longer required to download Cumulative updates.
To learn more about the release or servicing model, please visit:

• CU10 KB Article: https://support.microsoft.com/en-us/help/5001090

Starting with SQL Server 2017, we adopted a new modern servicing model. Please refer to our blog for more details on Modern Servicing Model for SQL Server

• Microsoft® SQL Server® 2019 RTM Latest Cumulative Update: https://www.microsoft.com/download/details.aspx?id=100809


• Update Center for Microsoft SQL Server: https://docs.microsoft.com/en-us/sql/database-engine/install-windows/latest-updates-for-microsoft-sql-server

Improving the Page Properties web part

by Contributed | Apr 6, 2021 | Technology

This article is contributed. See the original author and article here.

Ever get annoyed with the page properties web part put out by Microsoft?  If you’ve got some OCD issues (like me) then it may not take very long.  At ThreeWill, we help clients with their digital workplaces and improving the way their users can obtain information and makes sense of it all.  Oftentimes, the Page Properties web part can be useful here, as we very often add valuable metadata to pages in a digital workplace, which we often tie to page templates as well.  News might roll up based on these page properties, which can assist in finding information in many ways.  But its often handy to display this metadata in a clean way on a page as well.  The standard Page Properties web part seeks to do just that.  And, for the most part, it does a fine job with it.  But it has a few deficiencies.  The most annoying thing to me, when setting up digital workplaces was that it only supports a white background.  But there are other small things, like the limitations with pretty standard field types.  I like the idea of taking advantage of metadata columns for pages, but being able to use it visually is equally important.  I finally decided to do something about it and build a new version of this web part.   So with this in mind, let’s lay out our goals with this new web part.  We will call it the Advanced Page Properties web part.
 
Feature Goals
Attempt to replicate the functionality of Page Properties with the following improvements:

Support for theme variants
Updated to standard capsule look for list options
Support for image fields
Support for hyperlink fields
Support for currency
Improved support for dates
In other words, we’re shooting for this:

 
Property Pane
For a part like this, it’s all about getting the property page figured out first.  We want this to feel familiar too and not stray too much from the original design, unless it helps.
 
Let’s start by recognizing our chief property that the web part needs: selectedProperties.  This array will hold the internal names of the fields that a user has selected for display in our web part.  We intend on passing this property down to our React component.  Here’s a look at our property object:
 
 export interface IAdvancedPagePropertiesWebPartProps {
title: string;
selectedProperties: string[];
}
 
 
 
In our AdvancedPagePropertiesWebPart, we want to hold all possible properties for drop downs in a single array. 
 
 private availableProperties: IPropertyPaneDropdownOption[] = [];
 
 
 
Next, we need the following method to obtain the right types of properties for display:
 
&nbsp; private async getPageProperties(): Promise<VOID> {
Log.Write(“Getting Site Page fields…”);
const list = sp.web.lists.getByTitle(“Site Pages”);
const fi = await list.fields();

this.availableProperties = [];
Log.Write(`${fi.length.toString()} fields retrieved!`);
fi.forEach((f) =&gt; {
if (!f.FromBaseType &amp;&amp; !f.Hidden &amp;&amp; !f.Sealed &amp;&amp; f.SchemaXml.indexOf(“ShowInListSettings=”FALSE””) === -1
&amp;&amp; f.TypeAsString !== “Boolean” &amp;&amp; f.TypeAsString !== “Note” &amp;&amp; f.TypeAsString !== “User”) {
this.availableProperties.push({ key: f.InternalName, text: f.Title });
Log.Write(f.TypeAsString);
}
});
}
&nbsp;
&nbsp;
&nbsp;
We are using the PnP JS library for gathering the fields in the Site Pages library.&nbsp; Figuring out the right types of filters to gather was a bit of trial-and-error.&nbsp; We are excluding anything that’s inherited from a base type or is hidden in any way.&nbsp; We are also excluding 3 standard types so far: boolean, note and user.&nbsp; Note doesn’t make sense to display.&nbsp; Boolean can definitely work, but needs a good display convention.&nbsp; User was the only tricky object, which is the reason it isn’t done yet.
&nbsp;
We call the above method prior to loading up the property pane.
&nbsp;
&nbsp; protected async onPropertyPaneConfigurationStart(): Promise<VOID> {
Log.Write(`onPropertyPaneConfigurationStart`);
await this.getPageProperties();
this.context.propertyPane.refresh();
}
&nbsp;
&nbsp;
&nbsp;
We need handlers for adding and deleting a property and selecting a property from a dropdown.&nbsp; These methods make necessary changes to the selectedProperties array.
&nbsp;
&nbsp; protected onAddButtonClick (value: any) {
this.properties.selectedProperties.push(this.availableProperties[0].key.toString());
}

protected onDeleteButtonClick (value: any) {
Log.Write(value.toString());
var removed = this.properties.selectedProperties.splice(value, 1);
Log.Write(`${removed[0]} removed.`);
}

protected onPropertyPaneFieldChanged(propertyPath: string, oldValue: any, newValue: any): void {
if (propertyPath.indexOf(“selectedProperty”) &gt;= 0) {
Log.Write(‘Selected Property identified’);
let index: number = _.toInteger(propertyPath.replace(“selectedProperty”, “”));
this.properties.selectedProperties[index] = newValue;
}
}
&nbsp;
&nbsp;
&nbsp;
Finally, with all of our pieces in place, we can render our property pane with all it’s needed functionality.
&nbsp;
&nbsp; protected getPropertyPaneConfiguration(): IPropertyPaneConfiguration {
Log.Write(`getPropertyPaneConfiguration`);

// Initialize with the Title entry
var propDrops: IPropertyPaneField<ANY>[] = [];
propDrops.push(PropertyPaneTextField(‘title’, {
label: strings.TitleFieldLabel
}));
propDrops.push(PropertyPaneHorizontalRule());
// Determine how many page property dropdowns we currently have
this.properties.selectedProperties.forEach((prop, index) =&gt; {
propDrops.push(PropertyPaneDropdown(`selectedProperty${index.toString()}`,
{
label: strings.SelectedPropertiesFieldLabel,
options: this.availableProperties,
selectedKey: prop,
}));
// Every drop down gets its own delete button
propDrops.push(PropertyPaneButton(`deleteButton${index.toString()}`,
{
text: strings.PropPaneDeleteButtonText,
buttonType: PropertyPaneButtonType.Command,
icon: “RecycleBin”,
onClick: this.onDeleteButtonClick.bind(this, index)
}));
propDrops.push(PropertyPaneHorizontalRule());
});
// Always have the Add button
propDrops.push(PropertyPaneButton(‘addButton’,
{
text: strings.PropPaneAddButtonText,
buttonType: PropertyPaneButtonType.Command,
icon: “CirclePlus”,
onClick: this.onAddButtonClick.bind(this)
}));

return {
pages: [
{
header: {
description: strings.PropertyPaneDescription
},
groups: [
{
groupName: strings.SelectionGroupName,
groupFields: propDrops
}
]
}
]
};
}
&nbsp;
&nbsp;
&nbsp;
Our Component and Displaying our fields/values
Our React component needs to properly react to the list of selected properties changing.&nbsp; It also needs to react to our theme changing.&nbsp; I leveraged this awesome post from Hugo Bernier for the theming, so I will not cover that in-depth, although you will see how it’s being leveraged in the code snippets below.&nbsp; Here are the properties we plan to start with and respond to:
&nbsp;
&nbsp;export interface IAdvancedPagePropertiesProps {
context: WebPartContext;
title: string;
selectedProperties: string[];
themeVariant: IReadonlyTheme | undefined;
}
&nbsp;
&nbsp;
&nbsp;
We will track the state of our selected properties and their values with hooks.&nbsp; We want to trigger off of changes to our properties, so we will setup a reference to their current state.&nbsp; We will also establish our themeVariant and context at the start of our component.
&nbsp;
&nbsp; // Main state object for the life of this component – pagePropValues
const [pagePropValues, setPagePropValues] = useState<PAGEPROPERTY>([]);
const propsRef = useRef(props);

const { semanticColors }: IReadonlyTheme = props.themeVariant;

propsRef.current = props;

sp.setup({ spfxContext: props.context });
&nbsp;
&nbsp;
&nbsp;
So we are tracking the state of pagePropValues, which is an array of type PageProperty.&nbsp; What is PageProperty?
&nbsp;
&nbsp;import { IFieldInfo } from “@pnp/sp/fields”;

export interface PageProperty {
info: IFieldInfo;
values: any[];
}
&nbsp;
&nbsp;
&nbsp;
Our effect is looking to see when changes are made to the properties, then is peforming our core logic to refresh properties and values.
&nbsp;
&nbsp; /**
* @description Effects to fire whenever the properties change
*/
useEffect(() =&gt; {
refreshProperties();

return () =&gt; {
// No cleanup at this moment
};
}, [propsRef.current]);
&nbsp;
&nbsp;
&nbsp;
The core method is refreshProperties.&nbsp; It has 2 main calls it needs to make, whenever selected properties has changed: Establish any known metadata for each property that will assist in display and obtain all actual values for this property and the specific page id that we are viewing.
&nbsp;
&nbsp; /**
* refreshProperties
* @description Gets the actual values for any selected properties, along with critical field metadata and ultimately re-sets the pagePropValues state
*/
async function refreshProperties () {
var newSetOfValues: PageProperty[] = [];

if (props.selectedProperties !== undefined &amp;&amp; props.selectedProperties !== null) {
Log.Write(`${props.selectedProperties.length.toString()} properties used.`);

// Get the value(s) for the field from the list item itself
var allValues: any = {};
if (props.context.pageContext.listItem !== undefined &amp;&amp; props.context.pageContext.listItem !== null) {
allValues = await sp.web.lists.getByTitle(“Site Pages”).items.getById(props.context.pageContext.listItem.id).select(…props.selectedProperties).get();
console.log(allValues);
}

for (let i = 0; i &lt; props.selectedProperties.length; i++) {
const prop = props.selectedProperties[i];

Log.Write(`Selected Property: ${prop}`);

// Get field information, in case anything is needed in conjunction with value types
const field = await sp.web.lists.getByTitle(“Site Pages”).fields.getByInternalNameOrTitle(prop)();

// Establish the values array
var values: any[] = [];
if (allValues.hasOwnProperty(prop)) {
switch (field.TypeAsString) {
case “TaxonomyFieldTypeMulti”:
case “MultiChoice”:
values = _.clone(allValues[prop]);
break;
case “Thumbnail”:
values.push(JSON.parse(allValues[prop]));
break;

default:
// Default behavior is to treat it like a string
values.push(allValues[prop]);
break;
}
}

// Push the final setup of a PageProperty object
newSetOfValues.push({ info: field, values: […values] });
}

setPagePropValues({…newSetOfValues});
}
}
&nbsp;
&nbsp;
&nbsp;
As we loop through all of the properties that have been selected, we make calls with PnP JS to get all of the metadata per field and all of the values per field.&nbsp; The call to get all of the values can return with any number of data types, so we need to be prepared for that.&nbsp; This is why it is of type any[] to start.&nbsp; But this is also why we have a switch statement for certain outlier situations, where the line to set the array of any need to be done a little differently than the default.&nbsp; Our 3 known cases of needing to do something different are&nbsp;TaxonomyFieldTypeMulti, MultiChoice and Thumbnail.
&nbsp;
React and Display
Our function component returns the following:
&nbsp;
&nbsp; return (
<DIV classname=”{`${styles.advancedPageProperties}”>
{RenderTitle()}
{RenderPageProperties()}
</DIV>
);
&nbsp;
&nbsp;
&nbsp;
RenderTitle is pretty straightforward.
&nbsp;
&nbsp; /**
* RenderTitle
* @description Focuses on the 1 row layer, being the Title that has been chosen for the page
* @returns
*/
const RenderTitle = () =&gt; {
if (props.title !== ”) {
return <DIV classname=”{styles.title}”>{props.title}</DIV>;
} else {
return null;
}
};
&nbsp;
&nbsp;
&nbsp;
RenderPageProperties is the first of a 2-dimensional loop, where we want to display a section for each page property that was select, just like the original.
&nbsp;
&nbsp; **
* RenderPageProperties
* @description Focuses on the 2nd row layer, which is the property names that have been chosen to be displayed (uses Title as the display name)
* @returns
*/
const RenderPageProperties = () =&gt; {
if (pagePropValues !== undefined &amp;&amp; pagePropValues !== null) {
var retVal = _.map(pagePropValues, (prop) =&gt; {
return (
&lt;&gt;
<DIV classname=”{styles.propNameRow}”>{prop.info.Title}<SPAN style=”{{display:”> – {prop.info.TypeAsString}</SPAN></DIV>
<DIV classname=”{styles.propValsRow}”>
{RenderPagePropValue(prop)}
</DIV>

);
});
return retVal;
} else {
return <I>Nothing to display</I>;
}
};
&nbsp;
&nbsp;
&nbsp;
This method then calls our final display method, RenderPagePropValue, which peforms our 2nd layer of array display, mapping all of the values and providing the correct display, based on the field type of the selected property.&nbsp; This is the heart of the display, where various type conversions and logic are done real-time as we display the values, including trying to achieve a slightly more modern SharePoint look using capsules for array labels.
&nbsp;
&nbsp; /**
* RenderPagePropValue
* @description Focuses on the 3rd and final row layer, which is the actual values tied to any property displayed for the page
* @param prop
* @returns
*/
const RenderPagePropValue = (prop: PageProperty) =&gt; {
console.log(prop);
var retVal = _.map(prop.values, (val) =&gt; {
if (val !== null) {
switch (prop.info.TypeAsString) {
case “URL”:
return (
<SPAN classname=”{styles.urlValue}”><A href=”{val.Url}” target=”_blank” style=”{{color:” semanticcolors.link=””>{val.Description}</A></SPAN>
);
case “Thumbnail”:
return (
<SPAN><IMG classname=”{styles.imgValue}” src=”{val.serverRelativeUrl}” /></SPAN>
);
case “Number”:
return (
<SPAN classname=”{styles.plainValue}”>{(prop.info[“ShowAsPercentage”] === true ? Number(val).toLocaleString(undefined,{style: ‘percent’, minimumFractionDigits:0}) : (prop.info[“CommaSeparator”] === true ? val.toLocaleString(‘en’) : val.toString()))}</SPAN>
);
case “Currency”:
return (
<SPAN classname=”{styles.plainValue}”>{(prop.info[“CommaSeparator”] === true ? new Intl.NumberFormat(‘en-US’, { style: ‘currency’, currency: ‘USD’ }).format(val) : Intl.NumberFormat(‘en-US’, { style: ‘currency’, currency: ‘USD’, useGrouping: false }).format(val))}</SPAN>
);
case “DateTime”:
//,””,,
switch (prop.info[“DateFormat”]) {
case “StandardUS”:
return (
<SPAN classname=”{styles.plainValue}”>{new Date(val).toLocaleDateString()}</SPAN>
);
case “ISO8601”:
const d = new Date(val);
return (
<SPAN classname=”{styles.plainValue}”>{`${d.getFullYear().toString()}-${d.getMonth()}-${d.getDate()}`}</SPAN>
);
case “DayOfWeek”:
return (
<SPAN classname=”{styles.plainValue}”>{new Date(val).toLocaleDateString(“en-US”, { weekday: ‘long’, month: ‘long’, day: ‘numeric’, year: ‘numeric’ })}</SPAN>
);
case “MonthSpelled”:
return (
<SPAN classname=”{styles.plainValue}”>{new Date(val).toLocaleDateString(“en-US”, { month: ‘long’, day: ‘numeric’, year: ‘numeric’ })}</SPAN>
);
default:
return (
<SPAN classname=”{styles.plainValue}”>{new Date(val).toLocaleDateString()}</SPAN>
);
}
case “TaxonomyFieldTypeMulti”:
case “TaxonomyFieldType”:
return (
<SPAN classname=”{styles.standardCapsule}” style=”{{backgroundColor:” semanticcolors.accentbuttonbackground=””>{val.Label}</SPAN>
);
default:
return (
<SPAN classname=”{styles.standardCapsule}” style=”{{backgroundColor:” semanticcolors.accentbuttonbackground=””>{val}</SPAN>
);
}
} else {
return (<SPAN classname=”{styles.plainValue}”>N/A</SPAN>);
}
});
return retVal;
};
&nbsp;
&nbsp;
&nbsp;
&nbsp;
So that’s all of the necessary code.&nbsp; Here’s what the finished product looks like, compared to the original page properties web part.

&nbsp;
&nbsp;
This web part is now officially apart of the PnP Web Parts repository and can be found here.&nbsp; I would love to hear about improvements you’d like to see and obviously you are more than welcome to contribute.&nbsp; I already have a bit of a list of things I’d love to see it do.
&nbsp;
Other ideas for improvements:

Capsules to be linkable to either a search result page or a filtered view of site pages (we always get clien requests for this)
Support for People fields (this is the only thing lacking from the original)
Support for Boolean fields (just need the right idea for proper display, really)
Styling per property (ie. colorizing per property or something to that effect)
&nbsp;
Conclusion
Hopefully, I’ve gotten you excited about Page Properties again and you’ve learned a little along the way around how the current Page Properties part might be doing what it does under the hood.&nbsp; Please consider contributing and feel free to reach out to me anytime.&nbsp; Thanks for your time!
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;</PAGEPROPERTY></ANY></VOID></VOID>