Tech Tweedie

The Human Hack: Rebooting Consulting Culture

Fri, 02 Oct 2026 00:00:00 +0100

Baltic Power Platform Summit 2026

Thu, 24 Sep 2026 00:00:00 +0200

Manchester (All Day) D365PPUG - September 2026

Wed, 09 Sep 2026 08:45:00 +0100

Newcastle D365PPUG - September 2026

Thu, 03 Sep 2026 18:00:00 +0100

Copilot, Microsoft 365 & Power Platform Community Call - September 2026

Thu, 03 Sep 2026 07:00:00 -0700

EPPC26 - The Human Hack: The Future of Consulting Culture

Tue, 30 Jun 2026 15:15:00 +0200

The Human Hack: The Future of Consulting Culture

This isn’t about tools, templates, frameworks, or even just the latest AI technologies—it’s about people and mindset.

AI is driving a significant shift in the consulting landscape, encouraging a heightened focus on tools, templates, and frameworks at the risk of losing the human experience and mindset. In this honest and practical session, we explore how consultants and delivery leads can rediscover and develop better consulting cultures in a world obsessed with tools and delivery speed.

Speaking at Experts Live UK 2026

Fri, 12 Jun 2026 09:00:00 +0100

Newcastle D365PPUG - June 2026

Thu, 04 Jun 2026 18:00:00 +0100

Power Platform Build Backup Pipeline

Fri, 01 May 2026 12:00:00 +0100

name: $(TeamProject)_$(BuildDefinitionName)_$(SourceBranchName)_$(Date:yyyyMMdd)$(Rev:.r)

variables:
 - name: varPowerPlatformSPN
 value: Dataverse - Build - AzureDevOps
 - name: varPowerPlatformSPN2
 value: Dataverse - TracsIntegration-Build - AzureDevOps
 - name: varSolutionName
 value: TRACSCustomConnectors
 - name: varSolutionName2
 value: Entities
 - name: varSolutionName3
 value: Environment_Configuration
 - name: varSolutionName4
 value: Core
 - name: varSolutionName5
 value: Dataflows
 - name: varSolutionName6
 value: TRACS_Integration_Solution
 - name: varSolutionName7
 value: Document_Migration
 - name: varWebsiteId
 value: ca958ff8-3c4b-ee11-be6f-0022481ab062

## revert schedule to 0 once old build backup is retired
schedules:
 - cron: 30 13,18 * * 1-5
 displayName: Weekday Backup
 branches:
 include:
 - main
 always: true

trigger: none

pool:
 vmImage: 'windows-latest'

steps:
- checkout: self
 persistCredentials: true
 clean: true
- task: PowerPlatformToolInstaller@2
 inputs:
 DefaultVersion: true
 AddToolsToPath: true


## SOLUTION 1 - CUSTOM CONNECTORS
- task: PowerPlatformSetSolutionVersion@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName)'
 SolutionVersionNumber: '2.4.0.$(Build.BuildID)'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName)_managed.zip'
 Managed: true
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName).zip'
 Managed: false
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformUnpackSolution@2
 inputs:
 SolutionInputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName).zip'
 SolutionTargetFolder: '$(Build.SourcesDirectory)\src\solutions\$(varSolutionName)'
 SolutionType: 'Both'


## SOLUTION 2 - ENTITIES
- task: PowerPlatformSetSolutionVersion@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName2)'
 SolutionVersionNumber: '2.4.0.$(Build.BuildID)'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName2)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName2)_managed.zip'
 Managed: true
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName2)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName2).zip'
 Managed: false
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformUnpackSolution@2
 inputs:
 SolutionInputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName2).zip'
 SolutionTargetFolder: '$(Build.SourcesDirectory)\src\solutions\$(varSolutionName2)'
 SolutionType: 'Both'


## SOLUTION 3 - ENVIRONMENT CONFIGURATION
- task: PowerPlatformSetSolutionVersion@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName3)'
 SolutionVersionNumber: '2.4.0.$(Build.BuildID)'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName3)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName3)_managed.zip'
 Managed: true
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName3)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName3).zip'
 Managed: false
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformUnpackSolution@2
 inputs:
 SolutionInputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName3).zip'
 SolutionTargetFolder: '$(Build.SourcesDirectory)\src\solutions\$(varSolutionName3)'
 SolutionType: 'Both'


## SOLUTION 4 - CORE
- task: PowerPlatformSetSolutionVersion@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName4)'
 SolutionVersionNumber: '2.4.0.$(Build.BuildID)'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName4)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName4)_managed.zip'
 Managed: true
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName4)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName4).zip'
 Managed: false
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformUnpackSolution@2
 inputs:
 SolutionInputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName4).zip'
 SolutionTargetFolder: '$(Build.SourcesDirectory)\src\solutions\$(varSolutionName4)'
 SolutionType: 'Both'

## SOLUTION 5 - DATAFLOWS
- task: PowerPlatformSetSolutionVersion@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName5)'
 SolutionVersionNumber: '2.4.0.$(Build.BuildID)'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName5)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName5)_managed.zip'
 Managed: true
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName5)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName5).zip'
 Managed: false
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformUnpackSolution@2
 inputs:
 SolutionInputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName5).zip'
 SolutionTargetFolder: '$(Build.SourcesDirectory)\src\solutions\$(varSolutionName5)'
 SolutionType: 'Both'

## SOLUTION 6 - TRACS INTEGRATION
- task: PowerPlatformSetSolutionVersion@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN2)'
 SolutionName: '$(varSolutionName6)'
 SolutionVersionNumber: '2.4.0.$(Build.BuildID)'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN2)'
 SolutionName: '$(varSolutionName6)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName6)_managed.zip'
 Managed: true
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN2)'
 SolutionName: '$(varSolutionName6)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName6).zip'
 Managed: false
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformUnpackSolution@2
 inputs:
 SolutionInputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName6).zip'
 SolutionTargetFolder: '$(Build.SourcesDirectory)\src\tracsIntegrationSolutions\$(varSolutionName6)'
 SolutionType: 'Both'

# SOLUTION 7 - DOCUMENT MIGRATION
- task: PowerPlatformSetSolutionVersion@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName7)'
 SolutionVersionNumber: '2.4.0.$(Build.BuildID)'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName7)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName7)_managed.zip'
 Managed: true
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformExportSolution@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 SolutionName: '$(varSolutionName7)'
 SolutionOutputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName7).zip'
 Managed: false
 AsyncOperation: true
 MaxAsyncWaitTime: '60'
- task: PowerPlatformUnpackSolution@2
 inputs:
 SolutionInputFile: '$(Build.ArtifactStagingDirectory)\$(varSolutionName7).zip'
 SolutionTargetFolder: '$(Build.SourcesDirectory)\src\solutions\$(varSolutionName7)'
 SolutionType: 'Both'

## PORTAL
- task: PowerPlatformDownloadPaportal@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 DownloadPath: '$(Build.SourcesDirectory)\src\ppages'
 WebsiteId: '$(varWebsiteId)'
 Overwrite: true
 ModelVersion: 2


## REFERENCE DATA
- task: PowerPlatformExportData@2
 inputs:
 authenticationType: 'PowerPlatformSPN'
 PowerPlatformSPN: '$(varPowerPlatformSPN)'
 Environment: '$(BuildTools.EnvironmentUrl)'
 SchemaFile: '$(Build.SourcesDirectory)\referenceData\data_schema.xml'
 DataFile: '$(Build.ArtifactStagingDirectory)\$rferenceData.zip'
 Overwrite: true
- task: ExtractFiles@1
 inputs:
 archiveFilePatterns: '$(Build.ArtifactStagingDirectory)\$rferenceData.zip'
 destinationFolder: '$(Build.SourcesDirectory)\referenceData'
 cleanDestinationFolder: true
 overwriteExistingFiles: true


- task: CmdLine@2
 inputs:
 script: |
 echo commit all changes
 git config user.email "$(Build.RequestedForEmail)"
 git config user.name "$(Build.RequestedFor)"
 git checkout -b main
 git add --all
 git commit -m "Latest solution changes."
 echo push code to new repo
 git -c http.extraheader="AUTHORIZATION: bearer $(System.AccessToken)" push origin main

Power Platform EXPORT to DevOps - Complex Pipeline

Thu, 30 Apr 2026 12:00:00 +0100

📋 REUSABLE PATTERN
This document provides a proven, reusable pattern for implementing advanced Power Platform DevOps pipelines. Use this template to standardize and automate complex solution export, documentation, and version control processes.

Pattern Summary

Pattern Name: Power Platform Complex Solution Export Pipeline
Category: DevOps & CI/CD
Platform: Azure DevOps + Power Platform
Difficulty: Intermediate to Advanced
Time to Implement: 2-4 hours

What This Pattern Solves

Managing multiple interdependent solutions in a single pipeline.
Automating the export of Power Platform Portals and reference data.
Generating solution documentation automatically.
Cleaning up the repository before processing new solution versions.
Committing all unpacked solution components, portal data, and documentation to a new branch.

Pattern Outcomes

After implementing this pattern, you will have:

About Ian Tweedie

Sun, 05 Apr 2026 00:00:00 +0000

About Tech Tweedie

Hello, I’m Ian Tweedie, and welcome to my personal technical blog, Tech Tweedie.

I am a passionate technologist with a deep focus on the Microsoft Power Platform and Azure. This site is where I share my knowledge, experience, and insights gained from years of working with these powerful technologies.

My Mission

The purpose of this site is to provide high-quality, practical, and real-world technical content for developers, architects, and consultants working with the Power Platform. I aim to go beyond the basics, offering deep dives into complex topics, solutions to common challenges, and expert commentary on the future of low-code and pro-code development.

Contact

Sun, 05 Apr 2026 00:00:00 +0000

Contact Us

Thank you for your interest in Tech Tweedie. Whether you have a question, feedback, or a data protection inquiry, I’d love to hear from you.

General & Technical Inquiries

For questions about articles, technical topics, or speaking engagements, the best way to reach me is via social media or email.

Email: hello@tweed.technology
LinkedIn: https://www.linkedin.com/in/ian-tweedie/
Twitter/X: @iTweedie

Data Protection & Privacy Inquiries

For any questions related to our Privacy Policy, Cookie Policy, or your personal data, please email our dedicated privacy contact.

Cookie Policy

Sun, 05 Apr 2026 00:00:00 +0000

Last updated: 5 April 2026

This Cookie Policy explains how Tech Tweedie (“we”, “us”, and “our”) uses cookies and similar technologies to recognise you when you visit our website at https://techtweedie.github.io. It explains what these technologies are and why we use them, as well as your rights to control our use of them.

1. What are cookies?

A cookie is a small text file that a website saves on your computer or mobile device when you visit the site. It enables the website to remember your actions and preferences (such as login, language, font size, and other display preferences) over a period of time, so you don’t have to keep re-entering them whenever you come back to the site or browse from one page to another.

Privacy Policy

Sun, 05 Apr 2026 00:00:00 +0000

Privacy Policy

Last updated: 5 April 2026

This website, Tech Tweedie (accessible at https://techtweedie.github.io), is operated by:

Tweed Technology Ltd
Company Number: 07820713
Corporate website: https://tweed.technology/

Tweed Technology Ltd is the data controller responsible for your personal data under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

We are committed to protecting your privacy. This policy explains what personal data we collect, how we use it, and your rights concerning that data.

Terms of Use

Sun, 05 Apr 2026 00:00:00 +0000

Terms of Use

Last updated: 5 April 2026

Please read these Terms of Use (“Terms”) carefully before using the Tech Tweedie website (https://techtweedie.github.io) operated by Tweed Technology Ltd.

Your access to and use of the website is conditioned on your acceptance of and compliance with these Terms. These Terms apply to all visitors, users, and others who access or use the website.

By accessing or using the website, you agree to be bound by these Terms. If you disagree with any part of the terms, then you may not access the website.

Raiders of the Lost Consulting Ark: Revolutionizing CRM Workplace Culture

Wed, 18 Mar 2026 16:00:00 +0000

Power Platform EXPORT to DevOps - Simple Pipeline

Tue, 10 Mar 2026 00:00:00 +0100

📋 REUSABLE PATTERN
This document provides a proven, reusable pattern for implementing Power Platform DevOps pipelines. Use this template to standardize your solution export and version control processes across your organization.

Pattern Summary

Pattern Name: Power Platform Solution Export Pipeline
Category: DevOps & CI/CD
Platform: Azure DevOps + Power Platform
Difficulty: Beginner to Intermediate
Time to Implement: 1-2 hours

What This Pattern Solves

Manual solution exports prone to human error
Lack of version control for Power Platform solutions
Inconsistent deployment processes across environments
No audit trail for solution changes
Difficulty collaborating on Power Platform development

Pattern Outcomes

After implementing this pattern, you will have:

Power Platform IMPORT from DevOps - Simple Pipeline

Tue, 10 Mar 2026 00:00:00 +0100

📋 REUSABLE PATTERN
This document provides a proven, reusable pattern for implementing Power Platform solution deployment pipelines. Use this template to standardize your solution import and deployment processes across your organization.

Pattern Summary

Pattern Name: Power Platform Solution Import Pipeline
Category: DevOps & CI/CD
Platform: Azure DevOps + Power Platform
Difficulty: Beginner to Intermediate
Time to Implement: 1-2 hours

What This Pattern Solves

Manual solution deployments prone to human error
Inconsistent deployment processes across environments
Lack of automated testing after deployment
No standardized approach for environment-specific configurations
Difficulty maintaining deployment consistency across teams

Pattern Outcomes

After implementing this pattern, you will have:

Generate Power Platform Solution Documentation with Azure DevOps

Wed, 19 Nov 2025 00:00:00 +0000

🚀 Build Your First Azure DevOps Pipeline for Power Platform (Complete Beginner Tutorial!)

Tue, 18 Nov 2025 06:00:00 +0100

D365 & Power Platform UG North East – September 2025 Meetup

Tue, 30 Sep 2025 06:00:00 +0100

Playwright for Makers – Bringing One-Click UI Tests to Model-Driven Apps & Power Pages

Wed, 10 Sep 2025 06:00:00 +0100

Generate Power Platform Solution Documentation with Azure DevOps

Thu, 04 Sep 2025 06:00:00 +0100

Power Platform Clinic Episode 7: Automatically Tag DevOps Tickets by Email

Sun, 20 Jul 2025 00:00:00 +0100

Running ADVANCED Playwright Tests in Azure DevOps for Power Platform Apps

Tue, 15 Jul 2025 00:00:00 +0100

Power Platform Clinic - Episode 6: Certs, Consultancy, and Career Conversations

Sun, 13 Jul 2025 09:00:00 +0100

Running Playwright Tests in Azure DevOps for Power Platform Apps

Wed, 02 Jul 2025 00:00:00 +0100

Power Platform Clinic – Episode 5: Converting Forms with Images to PDF

Wed, 25 Jun 2025 00:00:00 +0100

Walkthrough Customising Entra External ID for Power Pages

Tue, 24 Jun 2025 06:00:00 +0100

Power Platform Clinic – Episode 4: Power Pages Authentication Options and Developer Accounts

Tue, 03 Jun 2025 00:00:00 +0100

D365 & Power Platform UG North East – June 2025 Meetup

Sun, 01 Jun 2025 06:00:00 +0100

Power Platform Clinic – Episode 3: Calling a Dad Joke API and Custom Visuals in Power BI Clinic

Mon, 26 May 2025 00:00:00 +0100

Walk through Power Pages with Entra External ID

Sun, 25 May 2025 06:00:00 +0100

At the Norfolk Power Platform User Group: Enabling Low-Code Developers to Create Custom Client Reports with a Helping Hand from Azure – Norfolk Power Platform User Group

Thu, 22 May 2025 06:00:00 +0100

Power Platform Clinic – Episode 2

Tue, 20 May 2025 00:00:00 +0100

Show and Hide Tabs Based on Status Reason in Model Driven Apps

Sat, 12 Apr 2025 00:00:00 +0000

Power Platform Clinic Episode 1

Sat, 12 Apr 2025 00:00:00 +0100

D365 & Power Platform UG North East – March 2025 Meetup

Thu, 27 Mar 2025 06:00:00 +0100

At the Scottish Power Platform User Group: Enabling Low-Code Developers to Create Custom Client Reports with a Helping Hand from Azure – Scottish Power Platform User Group

Tue, 25 Mar 2025 18:00:00 +0000

Set folder permissions in SharePoint with Power Automate Flow

Mon, 17 Feb 2025 11:06:00 +0100

Send Emails from Flow without a Service Account

Mon, 10 Feb 2025 09:00:00 +0100

At Birmingham Power Platform User Group: Enabling Low-Code Developers to Create Custom Client Reports with a Helping Hand from Azure – Norfolk Power Platform User Group

Thu, 30 Jan 2025 18:30:00 +0000

At Learner to Leader: Avoid Costly Mistakes: Backing Up Your Power Platform Development Environment

Sat, 14 Dec 2024 06:00:00 +0100

Enabling Low-Code Developers to Create Custom Client Reports with a Helping Hand from Azure – Low Code No Code Conference

Sat, 09 Nov 2024 00:00:00 +0000

Effortlessly Move Dataverse for Teams Solutions

Tue, 22 Oct 2024 07:00:00 +0100

At the Virtual Power Platform User Group Presenting - Avoid Costly Mistakes: Backing Up Your Power Platform Development Environment

Thu, 03 Oct 2024 18:00:00 +0100

Calculate Working Day

Tue, 24 Sep 2024 09:00:00 +0100

Backup Dataverse Development Environment

Tue, 03 Sep 2024 07:00:00 +0100

Securing Power Automate for Production

Mon, 05 Aug 2024 19:00:00 +0100

Command Bar to Call Custom Page in Model Driven App

Sun, 23 Jun 2024 19:32:41 +0100

Build a Basic PCF Field Control

Sun, 16 Jun 2024 19:32:41 +0100

How to Install Hugo on Windows 11

Tue, 04 Jun 2024 17:32:41 +0100

Power Platform Developer Tools Install Script

Tue, 04 Jun 2024 17:32:41 +0100

Variables in PowerFX Command Buttons

Fri, 24 May 2024 00:00:00 +0000

Clone with PowerFX Command button

Mon, 22 Apr 2024 19:00:00 +0100

Streamlining Webhook Testing

Fri, 09 Feb 2024 19:00:00 +0100

Create a Solution Configuration File

Wed, 07 Feb 2024 19:00:00 +0100

Bias of Maslow’s Hammer

Sat, 03 Feb 2024 19:00:00 +0100

Too Many Redirects on WordPress

Sun, 17 Sep 2023 19:00:00 +0100

Thinking Environment Meetings

Sun, 18 Dec 2022 19:00:00 +0100

Azure Function with Azure B2C

Wed, 14 Dec 2022 19:00:00 +0100

Postman to Azure Table Storage

Tue, 15 Nov 2022 19:00:00 +0100

Azure B2C oAuth on Postman

Mon, 14 Nov 2022 19:00:00 +0100

PFX certificate for FREE for Power Pages

Mon, 25 Jul 2022 19:00:00 +0100

Query Parameters on HTTP Trigger

Sun, 03 Apr 2022 19:00:00 +0100

Go বেসিক

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Mon, 01 Jan 0001 00:00:00 +0000

Hello World

A sample go program is show here.

package main

import "fmt"

func main() {
 message := greetMe("world")
 fmt.Println(message)
}

func greetMe(name string) string {
 return "Hello, " + name + "!"
}

Run the program as below:

$ go run hello.go

Variables

Normal Declaration:

var msg string
msg = "Hello"

Shortcut:

msg := "Hello"

Constants

const Phi = 1.618

Basic Types

Mon, 01 Jan 0001 00:00:00 +0000

Strings

str := "Hello"

Multiline string

str := `Multiline
string`

Numbers

Typical types

num := 3 // int
num := 3. // float64
num := 3 + 4i // complex128
num := byte('a') // byte (alias for uint8)

Other Types

var u uint = 7 // uint (unsigned)
var p float32 = 22.7 // 32-bit float

Arrays

// var numbers [5]int
numbers := [...]int{0, 0, 0, 0, 0}

Pointers

func main () {
 b := *getPointer()
 fmt.Println("Value is", b)

func getPointer () (myPointer *int) {
 a := 234
 return &a

a := new(int)
*a = 234

Pointers point to a memory location of a variable. Go is fully garbage-collected.

অ্যাডভান্সড

Mon, 01 Jan 0001 00:00:00 +0000

Flow Control

Mon, 01 Jan 0001 00:00:00 +0000

Condition

if day == "sunday" || day == "saturday" {
 rest()
} else if day == "monday" && isTired() {
 groan()
} else {
 work()
}

if _, err := doThing(); err != nil {
 fmt.Println("Uh oh")

Switch

switch day {
 case "sunday":
 // cases don't "fall through" by default!
 fallthrough

 case "saturday":
 rest()

 default:
 work()
}

Loop

for count := 0; count <= 10; count++ {
 fmt.Println("My counter is at", count)
}

entry := []string{"Jack","John","Jones"}
for i, val := range entry {
 fmt.Printf("At position %d, the character %s is present\n", i, val)

n := 0
x := 42
for n != x {
 n := guess()
}

File Manipulation

Mon, 01 Jan 0001 00:00:00 +0000

Condition

if day == "sunday" || day == "saturday" {
 rest()
} else if day == "monday" && isTired() {
 groan()
} else {
 work()
}

if _, err := doThing(); err != nil {
 fmt.Println("Uh oh")

Bash Variables

Mon, 01 Jan 0001 00:00:00 +0000

Variable

NAME="John"
echo $NAME
echo "$NAME"
echo "${NAME}

Condition

if [[ -z "$string" ]]; then
 echo "String is empty"
elif [[ -n "$string" ]]; then
 echo "String is not empty"
fi