phillipharding

/* eslint-disable @typescript-eslint/no-explicit-any */

/** Configuration options for caching behavior in the cache proxy service.
 *
 * @property {number} [ttlMs] - Time-to-live in milliseconds for cached entries. If not specified, entries may be cached indefinitely.
 * @property {string[]} [cacheMethods] - Array of method names that should have their results cached. If not specified, no methods will be cached by default.
 * @property {string[]} [invalidateOn] - Array of method names that, when called, should invalidate the cache. Useful for clearing cache after data mutations.
 * @property {(method: string, args: any[]) => string} [keyFn] - Custom function to generate cache keys based on the method name and arguments. If not provided, a default key generation strategy will be used.
 * @property {(method: string, args: any[]) => string[] | undefined} [deriveIdsFromArgs] - Function to extract entity IDs from method arguments, used for selective cache invalidation. Returns an array of IDs or undefined if no I

phillipharding

Query SharePoint List Items using the Graph API sites and lists

Uses a server relative site URL instead of a site id

Uses a list title instead of a list id

Expands the fields attribute and restricts the expanded fields to

• id
• Title
• Author (Created by)
• Editor (Modified by)

phillipharding

a=[
    { sortIdx: 5, value: "E"},
    { sortIdx: 6, value: "F"},
    { sortIdx: 1, value: "A"},
    { sortIdx: 4, value: "D"},
    { sortIdx: 3, value: "C"},
    { sortIdx: 2, value: "B"},
];

function move(elToMove, targetSortIdx) {

phillipharding

Upgrading a Functions App and Code-base to the v4 Runtime

References.

• Migrate apps from Azure Functions version 3.x to version 4.x
• Azure Functions runtime versions overview
• Work with Azure Functions Core Tools
• Durable Functions versions overview
• Extension bundles
• [Fix output data serialization format in Node.js functions #2007](https:

phillipharding

javascript:(function(){var a=new URL(window.location.href);"5"===a.searchParams.get("view")&&(a.hash?a.hash="":a.hash="view=13"),document.location=a.href})();

phillipharding

/** References:
 * https://www.npmjs.com/package/azure-ad-verify-token
 * https://github.com/justinlettau/azure-ad-verify-token
 * https://liangjunjiang.medium.com/verify-and-decode-azure-activity-directory-token-bc72cf7010bc
 * https://liangjunjiang.medium.com/azure-active-directory-api-v1-0-vs-v2-0-5c75fb2b1154
 * https://www.npmjs.com/package/jwks-rsa
 * https://www.npmjs.com/package/jsonwebtoken
 * https://www.voitanos.io/blog/validating-azure-ad-generated-oauth-tokens
 * 
 * NOTE: 

phillipharding

/*
  Hit 'ctrl + d' or 'cmd + d' to run the code, view console for results
*/
import { IWeb, sp, Web } from "@pnp/sp/presets/all";
import { HttpRequestError } from "./@pnp/odata";

const TranslatePnPError = async (opText: string, e) => {
  if (e?.isHttpRequestError) {
    const json = await (<HttpRequestError>e).response.json();
    const errorObject = typeof json["odata.error"] === "object" ? {...json["odata.error"]} : {...e};

phillipharding

<#
	Renew An Expired Clientsecret For A Sharepoint Addin/ACS App Registration

	WHEN A SHAREPOINT ADDIN/ACS APP REGISTRATION IS CREATED THE CLIENTSECRET IS SET TO EXPIRE IN 1 YEAR
	THIS SCRIPT WILL RENEW AN EXPIRED CLIENTSECRET WITH A VALUE THAT EXPIRES IN 3 YEARS

	.\msol-renewsharepointaddinsecret.ps1 -clientId "" -userName "" -userPassword "" 

#>
param (

phillipharding

console.clear();

const isEmptyString = (s) => { return (typeof s === "undefined") || (s === null) || (s.length < 1); };

camlCompareOp = "Or";
camlPredicate = "Contains";
options = {};
options.queryByUniqueIdentifier = "90911";
//options.queryByPayrollNumber = "90919";
//options.queryByLocation = "01-001";

phillipharding

Use SPFx to get a Delegated Access Token

Note the tokenAcquisitionEvent part of the code doesn't seem to work

Using this technique you can acquire a delegated access token for a resource, SharePoint or the Graph API, and pass that token onto a HTTP triggered Azure Functions endpoint for it to use to call the appropriate API.

This is a simple re-imagination of the on-behalf-of flow involving a secured Azure Functions endpoint then executing an OAuth on-behalf-of flow to exchange the received access token for one which can be used to call an API on behalf of the calling user.

Documented originally by Paolo Pialorsi and Joel Rodrigues