July 23, 2025 • 46 mins
- Release Plans Visualized by Jukka Niiranen
- PowerDocu for Copilot Studio in the works by Rene Modery
- Copilot Studio: How I Built A Generative Orchestration Agent by Matthew Devany
- Michael Keimeyer shared 🚨Copilot Studio makers - these new options will allow for extended use cases by Carsten Groth
- 🚀 New AI Power for Contracts! | Carsten Groth
- No Code Is Dead - The New Stack
- What I learned from my vibe-coding experiments? by Steve Mordue
- Power Platform API and SDKs: From UX-First to API-First
- Dataverse MCP Server: A Game Changer for AI-Driven Workflows by Julie Koesmarno
- Dataverse - ULTIMATE Data Models Guide by Sean Astrakhan
- 🚫 Stop using Fiddler to test your PCF components with Dynamics 365! by David Øvrelid
- How to Tell PCF Stories Betim Beja
- Savings in Power Automate (preview)
- Build Modern Single-Page Applications in Power Pages (Preview) by Neeraj Nandwana
- Contribute to Power Platform and Copilot Studio Architecture Center
- 🎧 Podcasts that keep me inspired in the Low-Code space by Johannes Enström
Be sure to subscribe so you don't miss a single episode of Power Platform BOOST!
Thank you for buying us a coffee: buymeacoffee.com
Podcast home page: https://powerplatformboost.com
Email: hello@powerplatformboost.com
Follow us!
Twitter: https://twitter.com/powerplatboost
Instagram: https://www.instagram.com/powerplatformboost/
LinkedIn: https://www.linkedin.com/company/powerplatboost/
Facebook: https://www.facebook.com/profile.php?id=100090444536122
Mastodon: https://mastodon.social/@powerplatboost
Mark as Played
Transcript
Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Nick (00:00):
Awesome and I love people that learn in public.
It's an expression I've heardbefore and that's a great way to
share and kind of get theencouragement and motivation,
Because you go in public and yousay you're going to build
something and people want to seeit.
They're going to hold youaccountable to it, so good job.
Ulrikke (00:17):
And then some people just don't care that they
announce that they're going todo something in public and never
, ever, ever do.
You know, some people are likethat.
I'm not going to point fingersor anything, but you know, some
people are weird like that, Iguess.
Nick (00:35):
In the fullness of time.
I'm sure you'll get to thesethings that we talked about in
(00:55):
the past.
Ulrikke (00:58):
Hello everyone and welcome to the Power Platform
Boost podcast, your timelysource of Power Platform news
and updates, with your hosts,Nick Doelman and Ulrikke Akerbæk
.
Hey, Nick.
Nick (01:10):
Hey, Ulrikke, how are you doing?
Ulrikke (01:11):
Yeah, I'm hot.
It's 30-something.
It's been full sun all week andhalf the week before, so it's
not normal here for it to bethis hot, but I love it.
I love every second, everysunray, everything.
It's just I'm baked, so if I'mnot fully functioning it's just
(01:32):
because my mind is a bit kind ofmush, but yeah, that's okay.
Nick (01:38):
Everybody's enjoying the summer vibes right now, I'm sure
.
And for those of you who don'tlike the heat, just remember six
months from now, when it'sminus 28 and you're freezing
your butts off.
Just think back to these daysthat you're experiencing right
now.
Ulrikke (01:53):
Yeah, exactly, but I'm happy either way.
I love snow and I love the cold, and I love the sun and I love
the heat.
Sometimes it does take a tollon my cognitive abilities, so
that's kind of just a bit of awaiver.
But yeah, how are you otherthan the weather?
Nick (02:09):
Oh yeah, doing great, basically doing a lot of working
.
I like to describe myself asworking on my business, not in
my business the last week or two, so really focusing on
rebranding work and learning newthings and things like that.
Just because I'm kind ofproject, work right now is kind
of a little bit on hold over thesummer, which is great, so it's
(02:30):
taking that opportunity tolearn new things and, of course,
other stuff as well going tothe gym training for the next
big powerlifting competition andexperiencing a few little aches
and pains here that I'm workingthrough with my coach, but for
the rest, I can't complain, lifeis good.
And then going to concerts aswell.
There's a big music festivalhere in Ottawa called Blues Fest
.
For those of you who I know wehave, I know I have listeners
(02:52):
from Ottawa, they know all aboutBlues Fest.
But we my daughter and I sawGreen Day on Friday night and it
was freaking awesome.
So good, just.
It was just such a great time.
The music, just everybodysinging along, the crowd
reacting.
It was probably one of the bestshows I've seen in a long time.
So, yeah, can't complain In agood spot here.
Ulrikke (03:16):
Fantastic.
I'm so envious they have kidsthat age that can go to those
kinds of concerts.
I can't wait for my kid to bethat age, so that's gonna be
good, yeah and and my kid wantsto go with me.
Nick (03:26):
She's like she was excited to like be with me at the.
It's always like it was atwo-way thing, so it's not like
you know.
She's kind of like oh, dad,you're coming.
It was more like yeah yeah,we're going.
We're gonna see green day andwe were listening we went on a
couple road trips last week and,of course, listening to spotify
the bands.
We're going to listen here andsee.
Yeah, it was really cool oh,that's awesome.
Ulrikke (03:46):
I'm so happy for you that you're having such a good
time and get a bit of kind ofsummer holiday feeling as well.
Uh, that's good.
I didn't.
Yeah, everyone needs it, and I,the more I talk to people
outside of kind of the nordics,that don't really know what the
kind of the common holiday thingis about, because we do take
full of july off, just everyoneat the same time and how that
works, the I yeah, it just makesme appreciate this system more
(04:10):
than I ever have before, really.
So, uh, yeah, because everyeveryone deserves a bit of
downtime and just absolutelydetox from all of it, um, every
now and again.
So it's so good.
Nick (04:22):
But we still get.
Ulrikke (04:24):
Yeah, exactly, but we don't stop, we just keep cooking
.
And we're going to give you ashow today as well, with the
news and updates, because solast week we had our Release
Notes episode, which of coursewe couldn't cover that and the
news and updates and our OneNoteis full of news articles from
the week and the week before.
So we just couldn't not do anepisode now just because there's
(04:47):
so many things to talk about.
So we will try to keep it shortand just talk about the most
important things that we kind ofdiscovered the last few weeks.
Nick (04:58):
So talk about the release plans and I think I'm just going
to segue, I'm going to jumpahead a little bit into in our
Power Platform section was awebsite that Yuka I'm not sure
it's not Yuka's site, but hepointed out but it's a site.
It's a community site, it'sactually a Power BI report, but
it's called releaseplansnet.
Have you ever seen this before?
It's really cool, basically.
Ulrikke (05:20):
Talked about it on the podcast before actually.
Nick (05:22):
Okay, oh yeah, I guess Absolutely You're right and it's
just, I guess, another littlereminder, because Yuka did do a
post on very much kind ofechoing what you said about
there wasn't a whole lot in thisparticular release wave and you
did some comparisons of thenumber of items and again
referred again to this websitethat shows the dashboard.
(05:43):
So it's a great resource foranybody following along and
wants to see what their favoritefeature or if their favorite
feature disappears before itgets released.
It's a good way to kind of keeptrack of these things.
So, again, we'll put that linkin the show notes so you guys
can check that out and use thatas kind of a follow along with
the release plan Because, as weknow, these things change.
And, of course, if you'vemissed it, check out our episode
(06:09):
from last week where we gothrough the release wave two and
we hear a go on a teenage rantabout not having enough, not
having enough news and updatesfor sure.
Ulrikke (06:15):
But luckily for me, the community pulls through and
give us more than enough thingsto talk about.
So, yeah, and not all news arekind of.
Some news are just small littlehighlights.
That just makes my day a teeny,weeny bit better.
For instance, rene Modery's postwhere he talks about because
(06:40):
he's the person behind PowerDocu.
And he's the person behindPowerDocu and if you don't know
what PowerDoc is, it's a toolyou can use to document your
Power Automate flows.
It's fantastic, it's phenomenal, and now I kind of use the
embedded chat co-pilot studio inPower Automate to kind of
(07:00):
document it.
But what PowerDocu will giveyou is a visual representation
of your flow.
And then he thought why can't Ido that with the Copa Studio
agents and chat and bots?
So that's what he's working onand it's not finished, it's not
(07:20):
out there yet, but he just poststhat on LinkedIn like this is
what I'm working on currentlyand what you get then is you get
feedback and you getencouragement and you get oh,
remember to add this thing.
And you get kind of engagementaround something to see how well
it resonates and just love tosee that kind of initiatives.
And also some of the commentsare like oh fantastic to finally
(07:43):
have a face to the name to thetool that I love.
So thank you for just pointingout that you were the guy behind
PowerDocu.
So I just wanted to shout out alittle bit to Renaitis, give
him a little limelight for theamazing job that he does.
Nick (07:59):
Awesome and I love people that learn in public.
It's an expression I've heardbefore and that's a great way to
share and kind of get theencouragement and motivation,
because you go in public and yousay you're going to build
something and people want to seeit.
They're going to hold youaccountable to it.
Ulrikke (08:14):
so, yeah, good job and then some people just don't care
that they announce that they'regoing to do something in public
and never, ever, ever do.
You know, some people are likethat.
I'm not gonna point fingers oranything, but you know it's uh.
Nick (08:28):
Some people are weird like that, I guess all in the uh, in
the fullness of time, I'm sureyou'll you'll get to these
things that we talked about inthe past yeah, but you do do
them.
Ulrikke (08:38):
That's the most irritating and impressive thing
about you.
So you just follow through, youjust do um.
Yeah, I wish I had the kind oftime that you got, because I
don't have a life.
That's what it is very funny,all right, okay.
So, moving on to something elsethat I saw on, oh, maybe, no,
okay, let me, I'll let you picksomething, so then we can just
go okay so we're talking aboutco-pilot studio, um, speaking
(09:01):
about learning in public andsharing stuff.
Nick (09:03):
Mat Matthew Devaney posted an amazing video on Copilot
Studio and it's titled how I howI built a generative
orchestration agent.
And this is something I want tosee more of this, because people
talk a lot about agents and yousee these demos that Microsoft
does and, oh, look, you get, getan agent to talk to your HR
system and do all this like kindof high level, I don't know
(09:25):
theoretical stuff.
Matthew wrote this agent thatbasically, is a way that you
could put in some emailaddresses and that will find
times to hold a meeting, likewithin your organization, and he
really amazingly broke it out,how he built it, how he had the
different topics going inCopilot Studio, how he did the
adaptive card to collect thisinformation.
It was just put together verygood.
(09:46):
To me, it was like, oh okay, Iwish we had more of these
examples of people buildinguseful agents, because I think
this is just going to helpinspire people and kick off
those creative sparks.
So thank you, matthew, for thatpost.
Again, we'll put that in theshow notes so you can check that
out for yourself if you'vemissed it.
Ulrikke (10:03):
So, yeah, really a great, great video yeah, very
good post and, of course,matthew is a pro.
So just watching his videos andhow he kind of goes through the
narrative and how he does itfor me that's half the thing
it's like, oh, such aprofessional and I just get
inspired by the work that hedoes, so it's very good.
Also, something in terms oftalking about agents.
I saw a good friend of mine,michael maymeyer.
(10:26):
We met at ebc this year.
He's an amazing photographer,always make sure to capture the
moment.
So I thank you, michael, forall the fantastic photos you
take when we're out and out in aboat on these conferences.
But also he's a great techieand he shared something that
Carson Gross shared this weekfrom the message center emails
(10:48):
that you get.
So when you're an admin inmessage centers I think I
mentioned this a couple ofepisodes ago as well you get
these emails as an admin withnews and updates, and Carson's
come into the habit of sharingthose out on LinkedIn for all of
the other people that aren'tadmins and doesn't get these
emails and can't see what's onthe message center.
Nick (11:06):
So one of these emails as they come into your inbox, like
or ignore those emails.
Ulrikke (11:11):
That's right, because there are a bazillion of them
and if you're an admin ofeverything, like global admin,
for instance, you get a lot ofthese.
Um, so two things you wanted tohighlight a single sign-on ssl
for external data sources foragents, so agents can now
connect to external data sourceswithout repeated manual
authentication, enablingsmoother and more secure
(11:32):
integrations.
And that means that we can nowauthenticate, kind of like a
connector that you can set thatup with your agent and then you
don't have to authenticate everytime that agent wants to use
that connector for the servicethat you want it to use.
And also, you can now publishyour agents to WhatsApp, which
is phenomenal, because we alluse WhatsApp for events
(11:52):
especially, right, it's a reallygood way of communicating and
also talks to the omni-channeltype experience that you want.
So that's really cool.
We want these agents to show upwhere we are and not the other
way around, so I think that'svery good news.
Nick (12:06):
Oh, that's amazing.
I'm not sure which technologyAir France uses, but what I love
about flying Air France is youcan actually communicate with
them through WhatsApp and youcan say I want to change this
flight, or here's my code andwhatever.
And it might be half an hourbefore they get back to you,
based on whether it's an agentdoing this or whether it's an
actual human, but it's just.
(12:27):
To me it's so much easier thanwaiting on the phone and waiting
.
You know the horrible elevatormusic and everything like that.
So the more we can see theseWhatsApp agents for just
customer service scenarios, Ithink it's a win-win for
everyone.
Ulrikke (12:39):
Oh yeah, yeah, 100%, and soon you'll have an agent
that you could just put in.
Get in touch with that agentand then off you go.
Maybe.
Nick (12:47):
Exactly.
Ulrikke (12:48):
Yeah, also something in terms of agent and kind of
legal perspective.
There was an announcement thisweek that you now have a new
contract processing pre-builtmodel in Power Automate that you
can use with Power Apps isactually AI Builder, that this
feature is kind of wrappedaround, where you just give it a
(13:12):
high resolution image of alegal document and then it will
process what comes out of it.
And they also introduced a termthat I haven't heard before,
ocr, which is optical characterrecognition, which is then it
reads the characters on theimage, optical character
(13:33):
recognition capabilities andanalyzing and extract key fields
from the contract entities.
So that is really neat.
Nick (13:41):
Have you not heard that term before?
Oh, okay, so that's becauseyou're young and I'm old.
That's been the term.
Ocr has been around for like athousand years.
I remember my first job when wewere doing material safety data
, building a material safetydata sheet database, and I won't
get too much of the technicaldetails, but I remember talking
(14:02):
about OCR at that time, but atthat time that the technology
was so bad.
You'd try to scan something andit just couldn't figure it out.
This is one of those thingswhere we'd spend months building
the software.
We actually had a team ofpeople that were rekeying the
actual faxes and whatever into adatabase, into a database, and
(14:27):
I just that's a situation.
If I look back at it now Icould build an app in an
afternoon that would basicallyreplace five of those people
that were working full-time allyear round and get the same
amount of work done in a day.
So yeah it.
Just when you said OCR, like,and you said it was a new term,
like, or did you say it was newto you?
Ulrikke (14:41):
but it was like wait a minute, I was new to me.
I see these acronyms all thetime and I see OKR mean other
things, but in this kind ofcontext, that's what it means
and I keep reminding myself tosay what things are, because
these acronyms kind of and alsoI don't want to be one of those
(15:01):
people that rant because ofacronyms, because that's how the
world goes around, but alsoit's important to speak it out,
to speak to what it is.
But yeah, so you had other newson local and AI stuff.
A few people that actually ranteven to the quality that we do
(15:22):
or better than we do.
Nick (15:22):
Yeah, and this is kind of have it under our section of AI
stuff there are people thatactually rant even to the
quality that we do or betterthan we do.
Yeah, and this is kind of haveit under our section of AI stuff
and of course, it changes on aweek-to-week basis in so many
things.
This was a post called no Codeis Dead.
It was on the newstackio.
It's been shared on LinkedIn byJoel Lindstrom, who is a former
MVP and well-known in thecommunity.
(15:44):
By Joel Lindstrom, who heformer MVP and well-known in the
community.
Ryan Cunningham was one of thefolks that were interviewed or
quoted in this article, with alot of different industry
leaders talking about, you know,the rise of vibe coding and
building applications in AI.
And just the title, of course,is very click-baity and of
course, I'm guilty because Iposted a video a couple months
(16:04):
ago basically saying you know,no code is dead loglib vibe
coding, which generated a littlebit of discussion.
But again it's going throughabout the evolution of apps and,
of course, being able to.
People are talking about ohwell, you know, ai can never do
(16:25):
as good of a job as a programmerto other ones basically saying,
yeah, ai is going to completelytake over the whole business
and everything like that.
Of course, some Ryan Cunninghamtalked about Microsoft's
position of them building moreagentic apps and kind of trying
to push that narrative and thatstory through, like less apps,
more agents kind of thing, andit was a really interesting read
.
It was a very long read so wewill put the link again in the
(16:46):
show notes, but it's interestingif this is something you're
following along and kind ofwondering where your future will
be.
So there's a lot of goodviewpoints that you can kind of
make your own decision on thisor kind of get your own
viewpoints.
What I found interesting on thisarticle was it was very focused
on app development exclusively.
They didn't really touch on alot on how AI, in my mind, in
terms of vibe coding, is alsogoing to help with going through
(17:08):
and optimizing for performance,locating bugs, checking for
security.
I think it's all of a biggerpackage.
But at the end of the day, asI'm playing more and more at
these tools, including PlanDesigner and some of these other
ones, I'm thinking we need tostill have the human
orchestrator or the humanshepherd or babysitter as it
generates this code, and I thinkyou do need to have a.
(17:30):
You don't have to benecessarily an expert, but
understand the logic of what AIis generating and as we
architect these solutions.
So it's really again kind ofkeeping that narrative going
about where we're going withapplications, and we talked
about this last week as well,about how we see the Power
Platform going with a lot ofthese new tools like the single
page applications and PowerPages, the you know code pages,
(17:52):
the code apps, all of this, allthis interesting stuff, so
interesting article.
Check it out as you're, as likeall of us, learning and trying
to absorb where the industry isgoing.
Ulrikke (18:04):
Yep, it is a.
It's something my mind keepsgoing in this loop when I read
these kinds of articles, becauseI agree, and then I think of
the consequences and like, yeah,maybe it's going to take my job
, and then I think what is thejob that I can never do?
And then it's, and then it'sjust kind of go full circle.
(18:24):
It's very interesting to see,kind of when the industry
leaders talk about where thisplatform is headed and what the
tools that we use every day asprofessionals, where it's moving
for us to be prepared forwhat's coming, and we talked
about this before how it's soimportant to kind of be in the
split where we keep our currenttools and knowledge up to date
(18:48):
with the current state of theproducts that we are using every
day, but also being able tokeep up with the new
developments.
Nick (18:55):
Yes, and remember folks, if you're a pro developer, don't
worry, AI is not going to takeyour job, but Steve Mordew may
take your job Moving on segueinginto the next article and this
kind of ties in a little bitwith this, and this is something
I think I talked about beforeand it's something I know.
Steve posted something onLinkedIn about how, since he's
(19:16):
no longer an MVP, his goal is tobe able to be mentioned on our
podcast.
Ulrikke (19:22):
So, steve, we're mentioning your name, as we have
so many times.
Nick (19:27):
Absolutely, but this is a great article.
Yeah, he should sponsor us.
What do you think?
Yeah, steve, are you gonna be asponsor for the boost podcast?
Ulrikke (19:37):
buy us a beer at least, and you'll get a rubber dock
and maybe a hug next time I seeyou.
Nick (19:42):
Yes, all right yeah, but you talked about these five
coding experiments and this issomething that I've been talked
about in.
This as well is with these newtools and like I would also
throw like plan designer.
This as well is with these newtools and like I would also
throw like plan designer intothis, too is with these tools
you can take some of these ideasthat you've had floating in
your head and, like what steveis saying, that he wouldn't
necessarily hire programmers todevelop it, but now he has
(20:03):
access to the tools that he cantry out some of these ideas, he
can build some of these proof ofconcepts, and that's basically
the kind of throwing that outthere as a, I think, kind of a
motivation for any of us.
Even if you're not technical,if you have an idea for an app,
even if it's not necessarilygoing to be in production, you
can start using some of thesetools within the Microsoft
ecosystem or even outside tobegin to build these things and
(20:24):
try them out.
And I think it's going to begreat for some customers because
they can build these proof ofconcepts, and it's all about
showing versus telling sometimes, right?
Well, here's this app that Ibuilt using this vibe coding
tool.
It's not perfect.
I would like it to do this, buthere you know, hand it over to
like you and I as solutionarchitects.
Here's kind of where we'regoing with this.
So very interesting Again theseare.
(20:46):
This is a year ago.
We wouldn't even be talkingabout this.
This is how fast these thingsare going.
So I think some of these toolsis really to help move app
development along very quicklyand also kind of allow for
things to be done a lot moreefficiently, not even just on
the AI tools, but just for thepure communication of designing
apps and agents and all of thisfun technology.
(21:07):
We can kind of get thesevisualization of these proof of
concepts or these MVPs built alot quicker and a lot faster.
Ulrikke (21:13):
Isn't Steve the one that kind of always ranted about
all the shitty little apps?
I think it's funny that, comingfrom someone who's ranted about
shitty little apps for likefive years straight now, he's
encouraging everyone to build afreaking app.
Steve, get your shit together.
Okay, it's not going to be anagent here and a thousand shitty
(21:33):
agents.
I've seen that.
Isn't that the article wementioned last time?
Nick (21:37):
Yeah, that's true.
Ulrikke (21:39):
Yeah, that's true, All right, so over to more, actually
more solid stuff.
The Power Platform is nowmoving, shifting gears
completely, and this issomething that all developers
should know and keep in mind.
I'm going to use words, I don'tknow what I mean.
So the title is PowerPath fromAPI and SDKs, from UX first to
(22:02):
API first, and this is a shiftfrom the whole platform, from
the whole platform.
So, yeah, so the article kindof what it starts off saying is
that Power Platform has kind ofbeen administered and set up and
configured through PowerPlatform Admin Center.
(22:23):
Having that UX first experiencehas been the entry point.
That's how we have admin anddiscovered and worked with Power
Platform traditionally, whatthey're actually doing today.
We're taking a bold stepforward.
We're transforming PowerPlatform into an API-first
ecosystem where every feature inPPAC is backed by a
(22:43):
well-documented, public,accessible API, which means that
you can now kind of it soundsto me like infrastructure as
code in a way where everythingthat you could do through PPAC
is now going to be accessiblethrough an API and it's actually
going to be API first.
So, which means that they'regoing to kind of make sure that
you can cover everything throughthe API and SDK, the software
(23:08):
developer toolkit.
Software developer toolkit.
They're going to be developertoolkits for all languages and
across all the products.
So they've now officiallylaunched at build the C-sharp
SDK and they're now going tojust build more of these for
TypeScript and Python andPlatform Admin through Logic
(23:30):
Apps and Power Automate.
There's going to be developerkits kind of for all, covering
all angles in Python andPlatform Admin through Logic
Apps and Power Automate.
There's going to be developerkits kind of for covering all
angles.
And then, of course, you haveCLI and PowerShell support and
you have the MCP server supportfor Power Platform.
And this is kind of huge, Ithink, to announce a shift this
big.
And also it kind of shows youfor me at least, and this is
(23:54):
just my opinion, keep in mindthis shows me where we're going.
So the UI bit is going away andwe had this conversation not so
long ago.
We talk about coding apps andall these apps and yeah, all of
that and that's going to replacethis here.
You're always going to need tosee your own systems.
No, you're not, Because who'sgoing to use it?
(24:18):
There's not going to be anyonewho has the job of collecting
and enriching that data.
It's going to be agents havingaccess to public APIs or
subscriptions to that kind ofinformation, storing the
metadata of who of these in thispublic repertoire is your
customers, for instance, keepingthat information up to date on
its own.
It's going to be agent to agentcommunication and data flow.
(24:41):
So the UI of everything.
Who's going to need a websitewhen all information you want to
produce as a company isaccessible through agents and
NAIs?
You just need a way ofproviding that information,
which is an MCP server, an 8Aprotocol.
That's what's going to be theUI.
There's not going to be a UIgoing forward.
(25:02):
It's a bold statement, but Ithink this is, and this is not
just the only sign that we'reseeing of this, but I think it's
a significant kind of signpostof where we're actually going.
My opinion statement you mightdisagree and I hope you do, so
you can get out of conversationabout it.
Nick (25:21):
Not completely, I still think in terms of the user
interface for the PPAC.
I don't see that going awayanytime soon, but what it does
mean is for those, a lot of thelet's take the initial, the
first ring of this by having theAI and the SDKs for that.
If you're going through, ifyou're creating things like you
(25:42):
want to set up a new developer,you have a new developer, you're
onboarding.
We've been in projects where wehave a new developer onboarded.
Of course, you know whetherwe're working.
If we're working on sharedenvironments, it's one thing,
but sometimes we want to get toa point where the developer can
have their own isolatedenvironment and the ALM and
things like that.
Well, that involves goingthrough creating a Dataverse
developer instance, assigningthem permissions, making sure
(26:02):
that's set up in the ALMpipelines, all of this stuff.
Now, if you've established yourown internal corporate policy
of those 10 steps that you needto do Now, you can write a
script to do that.
Here's the script new developerscript.
Boom, does all those things,sends out the emails that signs
of security, does all that stuff.
Because it's all API first.
(26:22):
That's sort of the first levelof this, and then I think you're
right in terms of now.
This is also.
Instead, we're going to get anagent to do this.
So it's like oh, we'reonboarding bob, as you know, a
new person in our company.
The agent will go out and beginbecause it has this api access
to be able to go do all thisstuff.
Now there might be still someapprovals as part of that
(26:42):
process and that kind of thing,but I think you're right.
The whole idea of building a uiinterface provided by microsoft
for this.
I think there will be one for awhile, but eventually we won't
need it because we have thoseAPIs.
So, whether we build our ownuser interface or we tie that
into our agent user interface ofthe agents, just talk in the
background and do all this stuff, it's kind of setting up the
(27:04):
platform for that.
So I don't think you're wrong,but I also think there still has
to be a way for a human tointerject with this.
So, whether it's a littlechatbot, it's probably going to
be more voice.
I would actually say, if youwant to see the future, take a
look at Star Trek, where they'relike, basically, computer, spin
me up a new dataverse instance.
Ulrikke (27:27):
Hey, here you go, but that's the same with me and
ChatGPT today.
I don't write to ChatGpt, Italk to it.
Nick (27:33):
Yeah, yeah, and it'll be the same thing like, hey, chat
gpt, I'm research, I like I'vebeen living in chat gpt and
co-pilot like all last week asI'm kind of building, doing
business planning and thingslike this.
And yeah, it's a conversation,it's not, it's not me.
Well, it is me thinking about alot of things, but it's
conversations.
It's asking me questions andwhat about this and articulating
all of this stuff.
(27:53):
And yeah, it's a it's aconversation.
But yeah, in the practical dayto day it's like I want to be
able to say, oh, I just boughtthis thing off Amazon, here's
the receipt, and the agent saysokay, and just runs with it,
kind of thing.
Right, so yeah, yeah.
Ulrikke (28:11):
And you imagine just going back to the topic of kind
of having that infrastructurecrash code approach to Power
Platform admin and PPAC.
How about going and saying,like you said, I'm going to
onboard PED or whatever it is,or why don't this new person
have access to this?
Or I need a new developer?
Remind me here.
Or you want to just prompt anagent for that and not going
through and do it and errorhandling, troubleshooting, all
(28:32):
those things.
If that agent actually works,then, yeah, that's what we're
used to and it's going to be thesame thing.
As you know, back in the daywhen we went from paper and you
think I'm not old when we wentfrom paper to digital, to the
computer, you know people likewell, I worked with some tourist
(28:53):
associations, right, and youcan imagine the small little
huts up in the Norwegianmountains.
They still have paper, you know, in this kind of folder thing,
right.
And then the youth come inthrough the summer and they want
to have a summer job and theygo what is this paper thing in
the pen?
Because they expect it to be anapp or it's something to do on
the computer, right?
(29:13):
So it's always been the case ofwhat you have at home is more
modern than what you have atwork, and the youth coming in
will expect digital tools to beable to work from everywhere.
So if you don't have SharePointin the cloud and you don't allow
for young people to work fromwherever they want, as a company
you're kind of stuck in the oldways and you kind of need to
keep up, and I think that'sgoing to be one of those same
(29:34):
things that actually we expectto be able to talk to an agent
soon on all levels.
So if you try to accesssomething and it's not
accessible through an agentexperience or a chat experience,
then you're just going to gowell, too bad for you because
I'm not going to use yourservices because it's not
accessible to me, because we'renot going to have that same way
(29:55):
of working with things that weused to.
Just a kind of a futuristicidea.
I think that's where we'reheading.
Yeah Right, you had a few otherposts here that I haven't been
looked into.
Nick (30:10):
Yeah, I'll just touch on them briefly because it does tie
into everything we're talkingabout.
So there's an article fromjulie cosamaro, who's she's on
the microsoft team, about thedataverse mcp server.
So we've already talked alittle bit about this and it
ties into agents and accessing.
So this is, if you're not surewhat the dataverse mcp server is
, this is an excellent articlethat walks you through what it
(30:31):
is, what it can do, talks abouta few experiments I did bring up
a few weeks ago.
Daniel Lakowicz has done somelabs on the Dataverse MCP server
.
I would recommend everybodyjust run through those quickly
it shouldn't even take you thatlong and that gives you a good
understanding of what this cando.
So that's something to checkout, or what Dataverse MCP
(30:52):
server really means.
Also, there's another article.
A quick shout out to SeanAstrakhan, who does the Solution
Architect Accelerator course,which I went through with Sean a
couple months ago.
It was amazing a lot of greatcontent.
I've been doing this for a longtime but of course you always
learn new things and newperspectives.
But he released a video onYouTube about Dataverse the
ultimate data models guide,talking about ERD diagrams and
(31:16):
things like that and building,you know, dataverse or data
infrastructures.
Despite the fact we have allthese tools and he talks about
them built within the PowerPlatform like a plan designer,
whatever, and it will create anERD for you.
It doesn't always do the bestjob and it is something that you
really need to think through.
So he gives an excellentoverview of how all this works.
I think Hudeng and a few othershave posted things on Dataverse
(31:38):
and different relationships andstuff.
So if you're getting new toDataverse there's been a lot of
content lately.
I think, regardless of agentsand AI and co-pilots and power
pages if you solidify yourDataverse knowledge, especially
now more than ever, it's justgoing to benefit you hugely in
your career in the powerplatform and beyond, because I
see Dataverse becoming a datasource for a lot of applications
(32:02):
and, with something with theDataverse MCP server, this opens
the door for you to buildapplications in your own
favorite tools and platforms.
Yet still talk to Dataverse.
Ulrikke (32:11):
So it's turning out to be the center of everything of
our universe, so to speak.
Yeah, and I absolutely 100%agree.
I listened to a podcast todaywhere they talked about research
being done with people.
They had a study with 54 peoplewhere they had some of them
could not use any tools, some ofthem could use Google but had
(32:31):
to write themselves, and somehad access to ChatGPT and then
they asked them to write a shortstory and then they tested them
afterwards and the people thatused ChatGPT couldn't really
actually tell the peoplestudying them kind of any exact
sentences or what that story wasabout.
People using Google and wroteto themselves could easily tell
(32:55):
back what the story was aboutwithout the tools accessible to
them.
And then they tested them overthe course of four months and
what turned out was that thepeople that had access to AI
tools and used that extensively,they lost the ability to create
those stories to the qualitythat they had in the past.
So they would kind of rate thestories and they deteriorated so
(33:21):
quickly and also to the pointwhere, when humans read through
the stories they created, theysaid that they felt cold and
distance and non-human, whichthen was actually rated by human
at the end um and also that.
And then they, they analyzedthe stories and they actually
adopted an ai llm way of writingwhich tells you something about
(33:44):
the deterioration of the humanmind.
Because the human mind andhuman body is designed to be
efficient If you're not usingsomething, like you know, with
muscle weight, weight trainingis very much a fresh commodity.
If you don't do it, itdisappears.
If the body thinks it doesn'tneed it, it removes it over time
.
If you don't train that muscle,then it will disappear.
(34:04):
This goes for ERD diagramscience as well.
If you never, if you stopdesigning your data models today
, it's not going to be longuntil you can't really do it
right and you're going to forgetabout all the small details
that you now, today, know how todo.
And then the guy on the podcastsaid so what do we do to prevent
(34:24):
this from happening?
And I said it's a simple answeryou can take the elevator every
single day or you can take thestairs.
It's your choice.
I choose to take the elevator.
Sometimes, when I'm tired, whenI'm stressed, when I'm carrying
a lot of weight or when I'mshort on time, I take the
elevator, but usually I take thestairs.
And so meaning to say do thework, and do the work every day
(34:48):
and keep your mind at the level,the quality that it is today,
when you need to, when it'sbeneficial for you to be more,
when you absolutely need to useAI to shortcut, to make things
faster.
But if you are starting to useit because you need better
quality of work, then you'recheating your own mind.
You're not cheating us, butyou're cheating your own mind.
(35:09):
So I just wanted to share thatto kind of give a bit of context
into what this is supposed tobe.
It is not supposed to replaceus, um, it's supposed to make us
more efficient, um, and if youlet it replace you, then you're
replacing yourself.
Nick (35:24):
Yeah, so yeah, yeah, no right, wow yeah, um, yeah, I,
that's very powerful, it's.
It's um, yeah, it kind oftriggered something about my
daughter actually had a sayingwhen we were going to like I
mentioned earlier, going tothese concerts, we took the
train because it was just somuch easier and going up a set
of stairs of course a lot ofpeople were taking the escalator
(35:45):
and it was just faster to takethe stairs and my daughter said
something really stuck with me.
She said 10% of people will nottake the stairs.
Let's be the 10%.
I'm like okay, love it.
Yes, be the 10%.
Be the 10%.
I'm like okay, love it.
Ulrikke (35:56):
Yes.
Nick (35:56):
Be the 10%.
Ulrikke (35:58):
Be the 10%.
So right, all right, let's goquickly through the rest of the
news, because we just dive intothese things, don't we?
I wanted to shout out to a, afriend of mine in the new agent
community, david, really, uh, heis now um created a tool called
(36:21):
the pcf cli proxy tool, andthis is how it works.
It is a proxy that interceptsthe requests to the bundle js
and then the request is reroutedto your local dev server.
It opens up in chrome with yourcrm and your latest code runs
in CRM.
So it's a way to trick whileyou are working on developing
(36:43):
your PCF component.
It will trick the system tothink that you're connected to
data as a proxy in between whileyou're working.
That's how I read it, and ifit's completely wrong, then,
david, please tell me off.
But I think that's what it is.
Then, david, please tell me off, but I think that's what it is.
And then I came across somethingcalled Tell PCF Stories by
(37:04):
Betim Beya, which is a storybook.
It's a front-end workshop forbuilding AI components and pages
in isolation.
It helps you develophard-to-reach statuses and edge
cases without needing to run thewhole app.
You can read more aboutStorybook in the official
website, so we'll put links tothat in the show notes if that
(37:26):
is something that you need todive more into.
Nick (37:30):
Do you have any other small?
Ulrikke (37:31):
little nuggets to share .
Nick (37:32):
No, no, I mean, that's a very common.
It's a common pattern whencreating javascript and model
driven apps to there is a way touse to use fiddler to redirect,
so you don't have to keepuploading and going through that
whole process.
So this is, this is great.
Um, like, yeah, pcf controlsare one of those things that
keep meaning to get more morelearning about, but uh, now that
(37:52):
you're diving into react.
Ulrikke (37:53):
It's going to be a piece of cake.
Nick (37:55):
Yes, absolutely, let's hope so Cool, all right, moving
along.
Ulrikke (38:00):
Right, okay, just saw something last week.
Do you remember when ChristineKolonis had her?
I think one of her first PowerApps was how to calculate how
much time a Power App no, sorry,power Automate saves you, how
much money it saves you.
No, she had it, it was meetings.
Nick (38:17):
No, no, power Automate saves you.
How much money it saves you?
No, she had it, it was meetings.
No, no, no, it was something ina meeting invite which
calculated how much money thatmeeting cost.
Ulrikke (38:26):
That's probably two years ago Now in Power Automate.
One of these days this week,something new popped up.
It was Savings it's called.
It was in preview.
I was was like, would you liketo enable savings?
I'm like, what is this?
It's a way for you to.
If you turn on savings for allyour power on my flows, then you
give it some parameters interms of how much manual time
(38:46):
would this take.
You uh, and then uh, you knowevery time it runs.
And then yeah, how many, what?
And then it will calculate howmuch money you've saved or how,
uh, much time you saved acrossall the group or on-main flows.
I love it.
It's so much fun.
It's one of the things I justwant to enable immediately at
our customers.
We have to talk about it whenwe get back after summer.
(39:08):
It's like onboarding flow.
How much time does it takeusually to onboard something?
Nick (39:15):
And then yeah, yeah, every time that runs that's, that's
awesome, that'd be so good,especially like people like oh
wow, the licensing is so likelook how much money you've saved
.
Like check this out you know,easy yep.
I think maybe that's where it'scoming from all, right now you
um, you put it there.
You put the pointed out herethe building modern single page
(39:36):
applications and PowerPagespreview.
We have talked about thisbefore.
I started to play a little bitwith it.
I actually installed the samplecode and played with that a bit
this week and it's yeah, Ithink this is again more to
report on this, but this isgoing to be a bit of a game
changer in terms of how anoption to build PowerPages, like
(39:56):
with React sites and thingslike that.
So I tried the credit card app.
You can get it on GitHub.
But, yeah, neeraj posted theblog post kind of explaining all
of this stuff too, sort of whatthat all means.
So, yeah, this was actuallyyour article.
Do you have your thoughts onthis?
Ulrikke (40:13):
No, I think actually it's one of those things that
just has floated in from one ofour old notes kind of things,
but it's, it's yeah, no, no,you're absolutely right.
Just keep in mind that thoseexample, those templates, they
aren't really connected to data.
So the data you're playingaround with you think it's real,
it's actually hard coded intothe, into the app.
(40:34):
So in those terms it's notreally best practice, but it's
done.
It's actually hard coded intothe, into the app.
So in those terms it's notreally best practice and but
it's done to kind of to help yousee how it can work.
Um, just kind of as a a bit ofa heads up for people because it
looks amazing.
Nick (40:46):
And then to actually hard code it yeah, well, the same,
yeah, this well, the sample I'veused actually did actually talk
to dataverse tables.
Um, you, actually you load asolution and the solution has
the tables there, so they're thecredit card applications and
stuff.
And then I was able to go backand and yeah, it's in the, it's
hard coded, hard coded in thecode in the sense of the table
names and everything.
But I was able to go into thedataverse and see the data
(41:09):
created from my sample site.
So maybe I think these thingslike the you look at the, the
log, these things are areconstantly being updated.
So maybe a previous example wasjust still static data.
Ulrikke (41:19):
I don't know, but yeah, it's coming along it's one of
those things that, in terms ofum, when you're developing um,
it's kind of hard because you'renot connected to it with the
real data which ties into thethings that we just talked about
.
So there are ways to to goaround it.
Um, yeah, let's just uh movequickly on to.
I saw something we talked aboutduring the release wave episode
(41:43):
how can you contribute, how canyou help kind of give back?
And then suddenly I saw on alink.
It was called Contribute toPower Platform and Copa Studio
Architecture Center, which is away to actually give feedback
and to help move these thingsalong To contribute to a new
article on the Power Platformand Copa Studio Architectural
(42:05):
Guide.
You can register your work andsubmit new GitHub issue and
contribute to a pattern to theArchitecture Center.
So they have some wordtemplates and they really want
to kind of get feedback and forus to reach out and contribute.
So we're going to put the linkin the show notes for that.
(42:27):
Excellent.
Nick (42:28):
If you want to have your name listed as a contributor in,
like Microsoft Learn, which myname still spattered because I
was an employee there, butthat's one way and, speaking,
that could also be if you're anaspiring or current Microsoft
Most Valuable Professional,which we both are, and still we
both got renewed.
Yes, whoop, whoop, whoop, whoop.
(42:49):
This is another way tocontribute.
So, but yeah, but if you havelike, even if you just have
random idea or not ideas, butthings to contribute, this is a
way to give the feedback toMicrosoft.
They are listening.
There's different channels tomake that happen.
Ulrikke (43:02):
Yeah, absolutely Okay.
Let's just wrap it up with alittle bit of a shout out that I
really love, Unless you havesomething else you want to
mention before we close off, gofor it.
I saw Johannes Enstrom, which isa Swede, I guess he which is
sweet, I guess.
He listed a few of podcaststhat keeps him inspired in the
low-code space, and then helisted our podcast at the top,
(43:23):
which I really appreciated.
So I want to say thank you forthat.
And then he also listed a fewothers that I wanted to mention
Go Down on Low-Code with RobKopolwicz and Ryan Duggan I
should have practiced thosenames A low-code approach, which
we have talked about before.
And then, of course, CRM Rockswith Marcus Ellenson, which have
(43:45):
both been guests on and he'sbeen going, for this has been
his since 2013.
So I mean, it's just a staplepodcast in our community and he
still keeps going.
It's just a staple podcast inour community and he still keeps
going.
It's amazing.
So a bit of shout out to bothJohannes and all the other
podcasts out there that keepeveryone up to date on the
(44:08):
latest news for Power Platform.
So that's very good.
Hello, Code.
Yes.
Nick (44:12):
Cool, all right.
So basically, yeah, I thinkwe're not going to.
I think, in terms of the events, yes, we're.
You know we're going to beparticipating in all those and
that's where you get your rubberduck.
The only one I want to shoutout is, if you're going to
register for the Power PlatformCommunity Conference in Las
Vegas, use BOOST100 to get $100discount to that off your ticket
(44:33):
.
But love to see you there andget your rubber duck from us.
Still have a big box full thatI'll be dragging with me and
yeah, and then our next episode.
We're still trying to adjustfor our summer schedule and
things like that, so we'll stillbe.
I think you just watch thesocials, we'll let you know, but
it will be on a Wednesday,either the 6th of August or the
(44:56):
following week.
At this point we haven't quitesolidified that just because
vacations and summer and youguys got a bonus episode from us
last week, so I don't want tohear any complaints.
Ulrikke (45:06):
I think it's all good.
Have a fantastic rest of yoursummer, guys, and we'll catch
you when we catch you.
Bye-bye, bye.
Nick (45:13):
Thank you for listening.
No-transcript.
Awesome and I love people that learn in public.
It's an expression I've heardbefore and that's a great way to
share and kind of get theencouragement and motivation,
Because you go in public and yousay you're going to build
something and people want to seeit.
They're going to hold youaccountable to it, so good job.
Ulrikke (00:17):
And then some people just don't care that they
announce that they're going todo something in public and never
, ever, ever do.
You know, some people are likethat.
I'm not going to point fingersor anything, but you know, some
people are weird like that, Iguess.
Nick (00:35):
In the fullness of time.
I'm sure you'll get to thesethings that we talked about in
(00:55):
the past.
Ulrikke (00:58):
Hello everyone and welcome to the Power Platform
Boost podcast, your timelysource of Power Platform news
and updates, with your hosts,Nick Doelman and Ulrikke Akerbæk
.
Hey, Nick.
Nick (01:10):
Hey, Ulrikke, how are you doing?
Ulrikke (01:11):
Yeah, I'm hot.
It's 30-something.
It's been full sun all week andhalf the week before, so it's
not normal here for it to bethis hot, but I love it.
I love every second, everysunray, everything.
It's just I'm baked, so if I'mnot fully functioning it's just
(01:32):
because my mind is a bit kind ofmush, but yeah, that's okay.
Nick (01:38):
Everybody's enjoying the summer vibes right now, I'm sure
.
And for those of you who don'tlike the heat, just remember six
months from now, when it'sminus 28 and you're freezing
your butts off.
Just think back to these daysthat you're experiencing right
now.
Ulrikke (01:53):
Yeah, exactly, but I'm happy either way.
I love snow and I love the cold, and I love the sun and I love
the heat.
Sometimes it does take a tollon my cognitive abilities, so
that's kind of just a bit of awaiver.
But yeah, how are you otherthan the weather?
Nick (02:09):
Oh yeah, doing great, basically doing a lot of working
.
I like to describe myself asworking on my business, not in
my business the last week or two, so really focusing on
rebranding work and learning newthings and things like that.
Just because I'm kind ofproject, work right now is kind
of a little bit on hold over thesummer, which is great, so it's
(02:30):
taking that opportunity tolearn new things and, of course,
other stuff as well going tothe gym training for the next
big powerlifting competition andexperiencing a few little aches
and pains here that I'm workingthrough with my coach, but for
the rest, I can't complain, lifeis good.
And then going to concerts aswell.
There's a big music festivalhere in Ottawa called Blues Fest
.
For those of you who I know wehave, I know I have listeners
(02:52):
from Ottawa, they know all aboutBlues Fest.
But we my daughter and I sawGreen Day on Friday night and it
was freaking awesome.
So good, just.
It was just such a great time.
The music, just everybodysinging along, the crowd
reacting.
It was probably one of the bestshows I've seen in a long time.
So, yeah, can't complain In agood spot here.
Ulrikke (03:16):
Fantastic.
I'm so envious they have kidsthat age that can go to those
kinds of concerts.
I can't wait for my kid to bethat age, so that's gonna be
good, yeah and and my kid wantsto go with me.
Nick (03:26):
She's like she was excited to like be with me at the.
It's always like it was atwo-way thing, so it's not like
you know.
She's kind of like oh, dad,you're coming.
It was more like yeah yeah,we're going.
We're gonna see green day andwe were listening we went on a
couple road trips last week and,of course, listening to spotify
the bands.
We're going to listen here andsee.
Yeah, it was really cool oh,that's awesome.
Ulrikke (03:46):
I'm so happy for you that you're having such a good
time and get a bit of kind ofsummer holiday feeling as well.
Uh, that's good.
I didn't.
Yeah, everyone needs it, and I,the more I talk to people
outside of kind of the nordics,that don't really know what the
kind of the common holiday thingis about, because we do take
full of july off, just everyoneat the same time and how that
works, the I yeah, it just makesme appreciate this system more
(04:10):
than I ever have before, really.
So, uh, yeah, because everyeveryone deserves a bit of
downtime and just absolutelydetox from all of it, um, every
now and again.
So it's so good.
Nick (04:22):
But we still get.
Ulrikke (04:24):
Yeah, exactly, but we don't stop, we just keep cooking
.
And we're going to give you ashow today as well, with the
news and updates, because solast week we had our Release
Notes episode, which of coursewe couldn't cover that and the
news and updates and our OneNoteis full of news articles from
the week and the week before.
So we just couldn't not do anepisode now just because there's
(04:47):
so many things to talk about.
So we will try to keep it shortand just talk about the most
important things that we kind ofdiscovered the last few weeks.
Nick (04:58):
So talk about the release plans and I think I'm just going
to segue, I'm going to jumpahead a little bit into in our
Power Platform section was awebsite that Yuka I'm not sure
it's not Yuka's site, but hepointed out but it's a site.
It's a community site, it'sactually a Power BI report, but
it's called releaseplansnet.
Have you ever seen this before?
It's really cool, basically.
Ulrikke (05:20):
Talked about it on the podcast before actually.
Nick (05:22):
Okay, oh yeah, I guess Absolutely You're right and it's
just, I guess, another littlereminder, because Yuka did do a
post on very much kind ofechoing what you said about
there wasn't a whole lot in thisparticular release wave and you
did some comparisons of thenumber of items and again
referred again to this websitethat shows the dashboard.
(05:43):
So it's a great resource foranybody following along and
wants to see what their favoritefeature or if their favorite
feature disappears before itgets released.
It's a good way to kind of keeptrack of these things.
So, again, we'll put that linkin the show notes so you guys
can check that out and use thatas kind of a follow along with
the release plan Because, as weknow, these things change.
And, of course, if you'vemissed it, check out our episode
(06:09):
from last week where we gothrough the release wave two and
we hear a go on a teenage rantabout not having enough, not
having enough news and updatesfor sure.
Ulrikke (06:15):
But luckily for me, the community pulls through and
give us more than enough thingsto talk about.
So, yeah, and not all news arekind of.
Some news are just small littlehighlights.
That just makes my day a teeny,weeny bit better.
For instance, rene Modery's postwhere he talks about because
(06:40):
he's the person behind PowerDocu.
And he's the person behindPowerDocu and if you don't know
what PowerDoc is, it's a toolyou can use to document your
Power Automate flows.
It's fantastic, it's phenomenal, and now I kind of use the
embedded chat co-pilot studio inPower Automate to kind of
(07:00):
document it.
But what PowerDocu will giveyou is a visual representation
of your flow.
And then he thought why can't Ido that with the Copa Studio
agents and chat and bots?
So that's what he's working onand it's not finished, it's not
(07:20):
out there yet, but he just poststhat on LinkedIn like this is
what I'm working on currentlyand what you get then is you get
feedback and you getencouragement and you get oh,
remember to add this thing.
And you get kind of engagementaround something to see how well
it resonates and just love tosee that kind of initiatives.
And also some of the commentsare like oh fantastic to finally
(07:43):
have a face to the name to thetool that I love.
So thank you for just pointingout that you were the guy behind
PowerDocu.
So I just wanted to shout out alittle bit to Renaitis, give
him a little limelight for theamazing job that he does.
Nick (07:59):
Awesome and I love people that learn in public.
It's an expression I've heardbefore and that's a great way to
share and kind of get theencouragement and motivation,
because you go in public and yousay you're going to build
something and people want to seeit.
They're going to hold youaccountable to it.
Ulrikke (08:14):
so, yeah, good job and then some people just don't care
that they announce that they'regoing to do something in public
and never, ever, ever do.
You know, some people are likethat.
I'm not gonna point fingers oranything, but you know it's uh.
Nick (08:28):
Some people are weird like that, I guess all in the uh, in
the fullness of time, I'm sureyou'll you'll get to these
things that we talked about inthe past yeah, but you do do
them.
Ulrikke (08:38):
That's the most irritating and impressive thing
about you.
So you just follow through, youjust do um.
Yeah, I wish I had the kind oftime that you got, because I
don't have a life.
That's what it is very funny,all right, okay.
So, moving on to something elsethat I saw on, oh, maybe, no,
okay, let me, I'll let you picksomething, so then we can just
go okay so we're talking aboutco-pilot studio, um, speaking
(09:01):
about learning in public andsharing stuff.
Nick (09:03):
Mat Matthew Devaney posted an amazing video on Copilot
Studio and it's titled how I howI built a generative
orchestration agent.
And this is something I want tosee more of this, because people
talk a lot about agents and yousee these demos that Microsoft
does and, oh, look, you get, getan agent to talk to your HR
system and do all this like kindof high level, I don't know
(09:25):
theoretical stuff.
Matthew wrote this agent thatbasically, is a way that you
could put in some emailaddresses and that will find
times to hold a meeting, likewithin your organization, and he
really amazingly broke it out,how he built it, how he had the
different topics going inCopilot Studio, how he did the
adaptive card to collect thisinformation.
It was just put together verygood.
(09:46):
To me, it was like, oh okay, Iwish we had more of these
examples of people buildinguseful agents, because I think
this is just going to helpinspire people and kick off
those creative sparks.
So thank you, matthew, for thatpost.
Again, we'll put that in theshow notes so you can check that
out for yourself if you'vemissed it.
Ulrikke (10:03):
So, yeah, really a great, great video yeah, very
good post and, of course,matthew is a pro.
So just watching his videos andhow he kind of goes through the
narrative and how he does itfor me that's half the thing
it's like, oh, such aprofessional and I just get
inspired by the work that hedoes, so it's very good.
Also, something in terms oftalking about agents.
I saw a good friend of mine,michael maymeyer.
(10:26):
We met at ebc this year.
He's an amazing photographer,always make sure to capture the
moment.
So I thank you, michael, forall the fantastic photos you
take when we're out and out in aboat on these conferences.
But also he's a great techieand he shared something that
Carson Gross shared this weekfrom the message center emails
(10:48):
that you get.
So when you're an admin inmessage centers I think I
mentioned this a couple ofepisodes ago as well you get
these emails as an admin withnews and updates, and Carson's
come into the habit of sharingthose out on LinkedIn for all of
the other people that aren'tadmins and doesn't get these
emails and can't see what's onthe message center.
Nick (11:06):
So one of these emails as they come into your inbox, like
or ignore those emails.
Ulrikke (11:11):
That's right, because there are a bazillion of them
and if you're an admin ofeverything, like global admin,
for instance, you get a lot ofthese.
Um, so two things you wanted tohighlight a single sign-on ssl
for external data sources foragents, so agents can now
connect to external data sourceswithout repeated manual
authentication, enablingsmoother and more secure
(11:32):
integrations.
And that means that we can nowauthenticate, kind of like a
connector that you can set thatup with your agent and then you
don't have to authenticate everytime that agent wants to use
that connector for the servicethat you want it to use.
And also, you can now publishyour agents to WhatsApp, which
is phenomenal, because we alluse WhatsApp for events
(11:52):
especially, right, it's a reallygood way of communicating and
also talks to the omni-channeltype experience that you want.
So that's really cool.
We want these agents to show upwhere we are and not the other
way around, so I think that'svery good news.
Nick (12:06):
Oh, that's amazing.
I'm not sure which technologyAir France uses, but what I love
about flying Air France is youcan actually communicate with
them through WhatsApp and youcan say I want to change this
flight, or here's my code andwhatever.
And it might be half an hourbefore they get back to you,
based on whether it's an agentdoing this or whether it's an
actual human, but it's just.
(12:27):
To me it's so much easier thanwaiting on the phone and waiting
.
You know the horrible elevatormusic and everything like that.
So the more we can see theseWhatsApp agents for just
customer service scenarios, Ithink it's a win-win for
everyone.
Ulrikke (12:39):
Oh yeah, yeah, 100%, and soon you'll have an agent
that you could just put in.
Get in touch with that agentand then off you go.
Maybe.
Nick (12:47):
Exactly.
Ulrikke (12:48):
Yeah, also something in terms of agent and kind of
legal perspective.
There was an announcement thisweek that you now have a new
contract processing pre-builtmodel in Power Automate that you
can use with Power Apps isactually AI Builder, that this
feature is kind of wrappedaround, where you just give it a
(13:12):
high resolution image of alegal document and then it will
process what comes out of it.
And they also introduced a termthat I haven't heard before,
ocr, which is optical characterrecognition, which is then it
reads the characters on theimage, optical character
(13:33):
recognition capabilities andanalyzing and extract key fields
from the contract entities.
So that is really neat.
Nick (13:41):
Have you not heard that term before?
Oh, okay, so that's becauseyou're young and I'm old.
That's been the term.
Ocr has been around for like athousand years.
I remember my first job when wewere doing material safety data
, building a material safetydata sheet database, and I won't
get too much of the technicaldetails, but I remember talking
(14:02):
about OCR at that time, but atthat time that the technology
was so bad.
You'd try to scan something andit just couldn't figure it out.
This is one of those thingswhere we'd spend months building
the software.
We actually had a team ofpeople that were rekeying the
actual faxes and whatever into adatabase, into a database, and
(14:27):
I just that's a situation.
If I look back at it now Icould build an app in an
afternoon that would basicallyreplace five of those people
that were working full-time allyear round and get the same
amount of work done in a day.
So yeah it.
Just when you said OCR, like,and you said it was a new term,
like, or did you say it was newto you?
Ulrikke (14:41):
but it was like wait a minute, I was new to me.
I see these acronyms all thetime and I see OKR mean other
things, but in this kind ofcontext, that's what it means
and I keep reminding myself tosay what things are, because
these acronyms kind of and alsoI don't want to be one of those
(15:01):
people that rant because ofacronyms, because that's how the
world goes around, but alsoit's important to speak it out,
to speak to what it is.
But yeah, so you had other newson local and AI stuff.
A few people that actually ranteven to the quality that we do
(15:22):
or better than we do.
Nick (15:22):
Yeah, and this is kind of have it under our section of AI
stuff there are people thatactually rant even to the
quality that we do or betterthan we do.
Yeah, and this is kind of haveit under our section of AI stuff
and of course, it changes on aweek-to-week basis in so many
things.
This was a post called no Codeis Dead.
It was on the newstackio.
It's been shared on LinkedIn byJoel Lindstrom, who is a former
MVP and well-known in thecommunity.
(15:44):
By Joel Lindstrom, who heformer MVP and well-known in the
community.
Ryan Cunningham was one of thefolks that were interviewed or
quoted in this article, with alot of different industry
leaders talking about, you know,the rise of vibe coding and
building applications in AI.
And just the title, of course,is very click-baity and of
course, I'm guilty because Iposted a video a couple months
(16:04):
ago basically saying you know,no code is dead loglib vibe
coding, which generated a littlebit of discussion.
But again it's going throughabout the evolution of apps and,
of course, being able to.
People are talking about ohwell, you know, ai can never do
(16:25):
as good of a job as a programmerto other ones basically saying,
yeah, ai is going to completelytake over the whole business
and everything like that.
Of course, some Ryan Cunninghamtalked about Microsoft's
position of them building moreagentic apps and kind of trying
to push that narrative and thatstory through, like less apps,
more agents kind of thing, andit was a really interesting read
.
It was a very long read so wewill put the link again in the
(16:46):
show notes, but it's interestingif this is something you're
following along and kind ofwondering where your future will
be.
So there's a lot of goodviewpoints that you can kind of
make your own decision on thisor kind of get your own
viewpoints.
What I found interesting on thisarticle was it was very focused
on app development exclusively.
They didn't really touch on alot on how AI, in my mind, in
terms of vibe coding, is alsogoing to help with going through
(17:08):
and optimizing for performance,locating bugs, checking for
security.
I think it's all of a biggerpackage.
But at the end of the day, asI'm playing more and more at
these tools, including PlanDesigner and some of these other
ones, I'm thinking we need tostill have the human
orchestrator or the humanshepherd or babysitter as it
generates this code, and I thinkyou do need to have a.
(17:30):
You don't have to benecessarily an expert, but
understand the logic of what AIis generating and as we
architect these solutions.
So it's really again kind ofkeeping that narrative going
about where we're going withapplications, and we talked
about this last week as well,about how we see the Power
Platform going with a lot ofthese new tools like the single
page applications and PowerPages, the you know code pages,
(17:52):
the code apps, all of this, allthis interesting stuff, so
interesting article.
Check it out as you're, as likeall of us, learning and trying
to absorb where the industry isgoing.
Ulrikke (18:04):
Yep, it is a.
It's something my mind keepsgoing in this loop when I read
these kinds of articles, becauseI agree, and then I think of
the consequences and like, yeah,maybe it's going to take my job
, and then I think what is thejob that I can never do?
And then it's, and then it'sjust kind of go full circle.
(18:24):
It's very interesting to see,kind of when the industry
leaders talk about where thisplatform is headed and what the
tools that we use every day asprofessionals, where it's moving
for us to be prepared forwhat's coming, and we talked
about this before how it's soimportant to kind of be in the
split where we keep our currenttools and knowledge up to date
(18:48):
with the current state of theproducts that we are using every
day, but also being able tokeep up with the new
developments.
Nick (18:55):
Yes, and remember folks, if you're a pro developer, don't
worry, AI is not going to takeyour job, but Steve Mordew may
take your job Moving on segueinginto the next article and this
kind of ties in a little bitwith this, and this is something
I think I talked about beforeand it's something I know.
Steve posted something onLinkedIn about how, since he's
(19:16):
no longer an MVP, his goal is tobe able to be mentioned on our
podcast.
Ulrikke (19:22):
So, steve, we're mentioning your name, as we have
so many times.
Nick (19:27):
Absolutely, but this is a great article.
Yeah, he should sponsor us.
What do you think?
Yeah, steve, are you gonna be asponsor for the boost podcast?
Ulrikke (19:37):
buy us a beer at least, and you'll get a rubber dock
and maybe a hug next time I seeyou.
Nick (19:42):
Yes, all right yeah, but you talked about these five
coding experiments and this issomething that I've been talked
about in.
This as well is with these newtools and like I would also
throw like plan designer.
This as well is with these newtools and like I would also
throw like plan designer intothis, too is with these tools
you can take some of these ideasthat you've had floating in
your head and, like what steveis saying, that he wouldn't
necessarily hire programmers todevelop it, but now he has
(20:03):
access to the tools that he cantry out some of these ideas, he
can build some of these proof ofconcepts, and that's basically
the kind of throwing that outthere as a, I think, kind of a
motivation for any of us.
Even if you're not technical,if you have an idea for an app,
even if it's not necessarilygoing to be in production, you
can start using some of thesetools within the Microsoft
ecosystem or even outside tobegin to build these things and
(20:24):
try them out.
And I think it's going to begreat for some customers because
they can build these proof ofconcepts, and it's all about
showing versus telling sometimes, right?
Well, here's this app that Ibuilt using this vibe coding
tool.
It's not perfect.
I would like it to do this, buthere you know, hand it over to
like you and I as solutionarchitects.
Here's kind of where we'regoing with this.
So very interesting Again theseare.
(20:46):
This is a year ago.
We wouldn't even be talkingabout this.
This is how fast these thingsare going.
So I think some of these toolsis really to help move app
development along very quicklyand also kind of allow for
things to be done a lot moreefficiently, not even just on
the AI tools, but just for thepure communication of designing
apps and agents and all of thisfun technology.
(21:07):
We can kind of get thesevisualization of these proof of
concepts or these MVPs built alot quicker and a lot faster.
Ulrikke (21:13):
Isn't Steve the one that kind of always ranted about
all the shitty little apps?
I think it's funny that, comingfrom someone who's ranted about
shitty little apps for likefive years straight now, he's
encouraging everyone to build afreaking app.
Steve, get your shit together.
Okay, it's not going to be anagent here and a thousand shitty
(21:33):
agents.
I've seen that.
Isn't that the article wementioned last time?
Nick (21:37):
Yeah, that's true.
Ulrikke (21:39):
Yeah, that's true, All right, so over to more, actually
more solid stuff.
The Power Platform is nowmoving, shifting gears
completely, and this issomething that all developers
should know and keep in mind.
I'm going to use words, I don'tknow what I mean.
So the title is PowerPath fromAPI and SDKs, from UX first to
(22:02):
API first, and this is a shiftfrom the whole platform, from
the whole platform.
So, yeah, so the article kindof what it starts off saying is
that Power Platform has kind ofbeen administered and set up and
configured through PowerPlatform Admin Center.
(22:23):
Having that UX first experiencehas been the entry point.
That's how we have admin anddiscovered and worked with Power
Platform traditionally, whatthey're actually doing today.
We're taking a bold stepforward.
We're transforming PowerPlatform into an API-first
ecosystem where every feature inPPAC is backed by a
(22:43):
well-documented, public,accessible API, which means that
you can now kind of it soundsto me like infrastructure as
code in a way where everythingthat you could do through PPAC
is now going to be accessiblethrough an API and it's actually
going to be API first.
So, which means that they'regoing to kind of make sure that
you can cover everything throughthe API and SDK, the software
(23:08):
developer toolkit.
Software developer toolkit.
They're going to be developertoolkits for all languages and
across all the products.
So they've now officiallylaunched at build the C-sharp
SDK and they're now going tojust build more of these for
TypeScript and Python andPlatform Admin through Logic
(23:30):
Apps and Power Automate.
There's going to be developerkits kind of for all, covering
all angles in Python andPlatform Admin through Logic
Apps and Power Automate.
There's going to be developerkits kind of for covering all
angles.
And then, of course, you haveCLI and PowerShell support and
you have the MCP server supportfor Power Platform.
And this is kind of huge, Ithink, to announce a shift this
big.
And also it kind of shows youfor me at least, and this is
(23:54):
just my opinion, keep in mindthis shows me where we're going.
So the UI bit is going away andwe had this conversation not so
long ago.
We talk about coding apps andall these apps and yeah, all of
that and that's going to replacethis here.
You're always going to need tosee your own systems.
No, you're not, Because who'sgoing to use it?
(24:18):
There's not going to be anyonewho has the job of collecting
and enriching that data.
It's going to be agents havingaccess to public APIs or
subscriptions to that kind ofinformation, storing the
metadata of who of these in thispublic repertoire is your
customers, for instance, keepingthat information up to date on
its own.
It's going to be agent to agentcommunication and data flow.
(24:41):
So the UI of everything.
Who's going to need a websitewhen all information you want to
produce as a company isaccessible through agents and
NAIs?
You just need a way ofproviding that information,
which is an MCP server, an 8Aprotocol.
That's what's going to be theUI.
There's not going to be a UIgoing forward.
(25:02):
It's a bold statement, but Ithink this is, and this is not
just the only sign that we'reseeing of this, but I think it's
a significant kind of signpostof where we're actually going.
My opinion statement you mightdisagree and I hope you do, so
you can get out of conversationabout it.
Nick (25:21):
Not completely, I still think in terms of the user
interface for the PPAC.
I don't see that going awayanytime soon, but what it does
mean is for those, a lot of thelet's take the initial, the
first ring of this by having theAI and the SDKs for that.
If you're going through, ifyou're creating things like you
(25:42):
want to set up a new developer,you have a new developer, you're
onboarding.
We've been in projects where wehave a new developer onboarded.
Of course, you know whetherwe're working.
If we're working on sharedenvironments, it's one thing,
but sometimes we want to get toa point where the developer can
have their own isolatedenvironment and the ALM and
things like that.
Well, that involves goingthrough creating a Dataverse
developer instance, assigningthem permissions, making sure
(26:02):
that's set up in the ALMpipelines, all of this stuff.
Now, if you've established yourown internal corporate policy
of those 10 steps that you needto do Now, you can write a
script to do that.
Here's the script new developerscript.
Boom, does all those things,sends out the emails that signs
of security, does all that stuff.
Because it's all API first.
(26:22):
That's sort of the first levelof this, and then I think you're
right in terms of now.
This is also.
Instead, we're going to get anagent to do this.
So it's like oh, we'reonboarding bob, as you know, a
new person in our company.
The agent will go out and beginbecause it has this api access
to be able to go do all thisstuff.
Now there might be still someapprovals as part of that
(26:42):
process and that kind of thing,but I think you're right.
The whole idea of building a uiinterface provided by microsoft
for this.
I think there will be one for awhile, but eventually we won't
need it because we have thoseAPIs.
So, whether we build our ownuser interface or we tie that
into our agent user interface ofthe agents, just talk in the
background and do all this stuff, it's kind of setting up the
(27:04):
platform for that.
So I don't think you're wrong,but I also think there still has
to be a way for a human tointerject with this.
So, whether it's a littlechatbot, it's probably going to
be more voice.
I would actually say, if youwant to see the future, take a
look at Star Trek, where they'relike, basically, computer, spin
me up a new dataverse instance.
Ulrikke (27:27):
Hey, here you go, but that's the same with me and
ChatGPT today.
I don't write to ChatGpt, Italk to it.
Nick (27:33):
Yeah, yeah, and it'll be the same thing like, hey, chat
gpt, I'm research, I like I'vebeen living in chat gpt and
co-pilot like all last week asI'm kind of building, doing
business planning and thingslike this.
And yeah, it's a conversation,it's not, it's not me.
Well, it is me thinking about alot of things, but it's
conversations.
It's asking me questions andwhat about this and articulating
all of this stuff.
(27:53):
And yeah, it's a it's aconversation.
But yeah, in the practical dayto day it's like I want to be
able to say, oh, I just boughtthis thing off Amazon, here's
the receipt, and the agent saysokay, and just runs with it,
kind of thing.
Right, so yeah, yeah.
Ulrikke (28:11):
And you imagine just going back to the topic of kind
of having that infrastructurecrash code approach to Power
Platform admin and PPAC.
How about going and saying,like you said, I'm going to
onboard PED or whatever it is,or why don't this new person
have access to this?
Or I need a new developer?
Remind me here.
Or you want to just prompt anagent for that and not going
through and do it and errorhandling, troubleshooting, all
(28:32):
those things.
If that agent actually works,then, yeah, that's what we're
used to and it's going to be thesame thing.
As you know, back in the daywhen we went from paper and you
think I'm not old when we wentfrom paper to digital, to the
computer, you know people likewell, I worked with some tourist
(28:53):
associations, right, and youcan imagine the small little
huts up in the Norwegianmountains.
They still have paper, you know, in this kind of folder thing,
right.
And then the youth come inthrough the summer and they want
to have a summer job and theygo what is this paper thing in
the pen?
Because they expect it to be anapp or it's something to do on
the computer, right?
(29:13):
So it's always been the case ofwhat you have at home is more
modern than what you have atwork, and the youth coming in
will expect digital tools to beable to work from everywhere.
So if you don't have SharePointin the cloud and you don't allow
for young people to work fromwherever they want, as a company
you're kind of stuck in the oldways and you kind of need to
keep up, and I think that'sgoing to be one of those same
(29:34):
things that actually we expectto be able to talk to an agent
soon on all levels.
So if you try to accesssomething and it's not
accessible through an agentexperience or a chat experience,
then you're just going to gowell, too bad for you because
I'm not going to use yourservices because it's not
accessible to me, because we'renot going to have that same way
(29:55):
of working with things that weused to.
Just a kind of a futuristicidea.
I think that's where we'reheading.
Yeah Right, you had a few otherposts here that I haven't been
looked into.
Nick (30:10):
Yeah, I'll just touch on them briefly because it does tie
into everything we're talkingabout.
So there's an article fromjulie cosamaro, who's she's on
the microsoft team, about thedataverse mcp server.
So we've already talked alittle bit about this and it
ties into agents and accessing.
So this is, if you're not surewhat the dataverse mcp server is
, this is an excellent articlethat walks you through what it
(30:31):
is, what it can do, talks abouta few experiments I did bring up
a few weeks ago.
Daniel Lakowicz has done somelabs on the Dataverse MCP server
.
I would recommend everybodyjust run through those quickly
it shouldn't even take you thatlong and that gives you a good
understanding of what this cando.
So that's something to checkout, or what Dataverse MCP
(30:52):
server really means.
Also, there's another article.
A quick shout out to SeanAstrakhan, who does the Solution
Architect Accelerator course,which I went through with Sean a
couple months ago.
It was amazing a lot of greatcontent.
I've been doing this for a longtime but of course you always
learn new things and newperspectives.
But he released a video onYouTube about Dataverse the
ultimate data models guide,talking about ERD diagrams and
(31:16):
things like that and building,you know, dataverse or data
infrastructures.
Despite the fact we have allthese tools and he talks about
them built within the PowerPlatform like a plan designer,
whatever, and it will create anERD for you.
It doesn't always do the bestjob and it is something that you
really need to think through.
So he gives an excellentoverview of how all this works.
I think Hudeng and a few othershave posted things on Dataverse
(31:38):
and different relationships andstuff.
So if you're getting new toDataverse there's been a lot of
content lately.
I think, regardless of agentsand AI and co-pilots and power
pages if you solidify yourDataverse knowledge, especially
now more than ever, it's justgoing to benefit you hugely in
your career in the powerplatform and beyond, because I
see Dataverse becoming a datasource for a lot of applications
(32:02):
and, with something with theDataverse MCP server, this opens
the door for you to buildapplications in your own
favorite tools and platforms.
Yet still talk to Dataverse.
Ulrikke (32:11):
So it's turning out to be the center of everything of
our universe, so to speak.
Yeah, and I absolutely 100%agree.
I listened to a podcast todaywhere they talked about research
being done with people.
They had a study with 54 peoplewhere they had some of them
could not use any tools, some ofthem could use Google but had
(32:31):
to write themselves, and somehad access to ChatGPT and then
they asked them to write a shortstory and then they tested them
afterwards and the people thatused ChatGPT couldn't really
actually tell the peoplestudying them kind of any exact
sentences or what that story wasabout.
People using Google and wroteto themselves could easily tell
(32:55):
back what the story was aboutwithout the tools accessible to
them.
And then they tested them overthe course of four months and
what turned out was that thepeople that had access to AI
tools and used that extensively,they lost the ability to create
those stories to the qualitythat they had in the past.
So they would kind of rate thestories and they deteriorated so
(33:21):
quickly and also to the pointwhere, when humans read through
the stories they created, theysaid that they felt cold and
distance and non-human, whichthen was actually rated by human
at the end um and also that.
And then they, they analyzedthe stories and they actually
adopted an ai llm way of writingwhich tells you something about
(33:44):
the deterioration of the humanmind.
Because the human mind andhuman body is designed to be
efficient If you're not usingsomething, like you know, with
muscle weight, weight trainingis very much a fresh commodity.
If you don't do it, itdisappears.
If the body thinks it doesn'tneed it, it removes it over time
.
If you don't train that muscle,then it will disappear.
(34:04):
This goes for ERD diagramscience as well.
If you never, if you stopdesigning your data models today
, it's not going to be longuntil you can't really do it
right and you're going to forgetabout all the small details
that you now, today, know how todo.
And then the guy on the podcastsaid so what do we do to prevent
(34:24):
this from happening?
And I said it's a simple answeryou can take the elevator every
single day or you can take thestairs.
It's your choice.
I choose to take the elevator.
Sometimes, when I'm tired, whenI'm stressed, when I'm carrying
a lot of weight or when I'mshort on time, I take the
elevator, but usually I take thestairs.
And so meaning to say do thework, and do the work every day
(34:48):
and keep your mind at the level,the quality that it is today,
when you need to, when it'sbeneficial for you to be more,
when you absolutely need to useAI to shortcut, to make things
faster.
But if you are starting to useit because you need better
quality of work, then you'recheating your own mind.
You're not cheating us, butyou're cheating your own mind.
(35:09):
So I just wanted to share thatto kind of give a bit of context
into what this is supposed tobe.
It is not supposed to replaceus, um, it's supposed to make us
more efficient, um, and if youlet it replace you, then you're
replacing yourself.
Nick (35:24):
Yeah, so yeah, yeah, no right, wow yeah, um, yeah, I,
that's very powerful, it's.
It's um, yeah, it kind oftriggered something about my
daughter actually had a sayingwhen we were going to like I
mentioned earlier, going tothese concerts, we took the
train because it was just somuch easier and going up a set
of stairs of course a lot ofpeople were taking the escalator
(35:45):
and it was just faster to takethe stairs and my daughter said
something really stuck with me.
She said 10% of people will nottake the stairs.
Let's be the 10%.
I'm like okay, love it.
Yes, be the 10%.
Be the 10%.
I'm like okay, love it.
Ulrikke (35:56):
Yes.
Nick (35:56):
Be the 10%.
Ulrikke (35:58):
Be the 10%.
So right, all right, let's goquickly through the rest of the
news, because we just dive intothese things, don't we?
I wanted to shout out to a, afriend of mine in the new agent
community, david, really, uh, heis now um created a tool called
(36:21):
the pcf cli proxy tool, andthis is how it works.
It is a proxy that interceptsthe requests to the bundle js
and then the request is reroutedto your local dev server.
It opens up in chrome with yourcrm and your latest code runs
in CRM.
So it's a way to trick whileyou are working on developing
(36:43):
your PCF component.
It will trick the system tothink that you're connected to
data as a proxy in between whileyou're working.
That's how I read it, and ifit's completely wrong, then,
david, please tell me off.
But I think that's what it is.
Then, david, please tell me off, but I think that's what it is.
And then I came across somethingcalled Tell PCF Stories by
(37:04):
Betim Beya, which is a storybook.
It's a front-end workshop forbuilding AI components and pages
in isolation.
It helps you develophard-to-reach statuses and edge
cases without needing to run thewhole app.
You can read more aboutStorybook in the official
website, so we'll put links tothat in the show notes if that
(37:26):
is something that you need todive more into.
Nick (37:30):
Do you have any other small?
Ulrikke (37:31):
little nuggets to share .
Nick (37:32):
No, no, I mean, that's a very common.
It's a common pattern whencreating javascript and model
driven apps to there is a way touse to use fiddler to redirect,
so you don't have to keepuploading and going through that
whole process.
So this is, this is great.
Um, like, yeah, pcf controlsare one of those things that
keep meaning to get more morelearning about, but uh, now that
(37:52):
you're diving into react.
Ulrikke (37:53):
It's going to be a piece of cake.
Nick (37:55):
Yes, absolutely, let's hope so Cool, all right, moving
along.
Ulrikke (38:00):
Right, okay, just saw something last week.
Do you remember when ChristineKolonis had her?
I think one of her first PowerApps was how to calculate how
much time a Power App no, sorry,power Automate saves you, how
much money it saves you.
No, she had it, it was meetings.
Nick (38:17):
No, no, power Automate saves you.
How much money it saves you?
No, she had it, it was meetings.
No, no, no, it was something ina meeting invite which
calculated how much money thatmeeting cost.
Ulrikke (38:26):
That's probably two years ago Now in Power Automate.
One of these days this week,something new popped up.
It was Savings it's called.
It was in preview.
I was was like, would you liketo enable savings?
I'm like, what is this?
It's a way for you to.
If you turn on savings for allyour power on my flows, then you
give it some parameters interms of how much manual time
(38:46):
would this take.
You uh, and then uh, you knowevery time it runs.
And then yeah, how many, what?
And then it will calculate howmuch money you've saved or how,
uh, much time you saved acrossall the group or on-main flows.
I love it.
It's so much fun.
It's one of the things I justwant to enable immediately at
our customers.
We have to talk about it whenwe get back after summer.
(39:08):
It's like onboarding flow.
How much time does it takeusually to onboard something?
Nick (39:15):
And then yeah, yeah, every time that runs that's, that's
awesome, that'd be so good,especially like people like oh
wow, the licensing is so likelook how much money you've saved
.
Like check this out you know,easy yep.
I think maybe that's where it'scoming from all, right now you
um, you put it there.
You put the pointed out herethe building modern single page
(39:36):
applications and PowerPagespreview.
We have talked about thisbefore.
I started to play a little bitwith it.
I actually installed the samplecode and played with that a bit
this week and it's yeah, Ithink this is again more to
report on this, but this isgoing to be a bit of a game
changer in terms of how anoption to build PowerPages, like
(39:56):
with React sites and thingslike that.
So I tried the credit card app.
You can get it on GitHub.
But, yeah, neeraj posted theblog post kind of explaining all
of this stuff too, sort of whatthat all means.
So, yeah, this was actuallyyour article.
Do you have your thoughts onthis?
Ulrikke (40:13):
No, I think actually it's one of those things that
just has floated in from one ofour old notes kind of things,
but it's, it's yeah, no, no,you're absolutely right.
Just keep in mind that thoseexample, those templates, they
aren't really connected to data.
So the data you're playingaround with you think it's real,
it's actually hard coded intothe, into the app.
(40:34):
So in those terms it's notreally best practice, but it's
done.
It's actually hard coded intothe, into the app.
So in those terms it's notreally best practice and but
it's done to kind of to help yousee how it can work.
Um, just kind of as a a bit ofa heads up for people because it
looks amazing.
Nick (40:46):
And then to actually hard code it yeah, well, the same,
yeah, this well, the sample I'veused actually did actually talk
to dataverse tables.
Um, you, actually you load asolution and the solution has
the tables there, so they're thecredit card applications and
stuff.
And then I was able to go backand and yeah, it's in the, it's
hard coded, hard coded in thecode in the sense of the table
names and everything.
But I was able to go into thedataverse and see the data
(41:09):
created from my sample site.
So maybe I think these thingslike the you look at the, the
log, these things are areconstantly being updated.
So maybe a previous example wasjust still static data.
Ulrikke (41:19):
I don't know, but yeah, it's coming along it's one of
those things that, in terms ofum, when you're developing um,
it's kind of hard because you'renot connected to it with the
real data which ties into thethings that we just talked about
.
So there are ways to to goaround it.
Um, yeah, let's just uh movequickly on to.
I saw something we talked aboutduring the release wave episode
(41:43):
how can you contribute, how canyou help kind of give back?
And then suddenly I saw on alink.
It was called Contribute toPower Platform and Copa Studio
Architecture Center, which is away to actually give feedback
and to help move these thingsalong To contribute to a new
article on the Power Platformand Copa Studio Architectural
(42:05):
Guide.
You can register your work andsubmit new GitHub issue and
contribute to a pattern to theArchitecture Center.
So they have some wordtemplates and they really want
to kind of get feedback and forus to reach out and contribute.
So we're going to put the linkin the show notes for that.
(42:27):
Excellent.
Nick (42:28):
If you want to have your name listed as a contributor in,
like Microsoft Learn, which myname still spattered because I
was an employee there, butthat's one way and, speaking,
that could also be if you're anaspiring or current Microsoft
Most Valuable Professional,which we both are, and still we
both got renewed.
Yes, whoop, whoop, whoop, whoop.
(42:49):
This is another way tocontribute.
So, but yeah, but if you havelike, even if you just have
random idea or not ideas, butthings to contribute, this is a
way to give the feedback toMicrosoft.
They are listening.
There's different channels tomake that happen.
Ulrikke (43:02):
Yeah, absolutely Okay.
Let's just wrap it up with alittle bit of a shout out that I
really love, Unless you havesomething else you want to
mention before we close off, gofor it.
I saw Johannes Enstrom, which isa Swede, I guess he which is
sweet, I guess.
He listed a few of podcaststhat keeps him inspired in the
low-code space, and then helisted our podcast at the top,
(43:23):
which I really appreciated.
So I want to say thank you forthat.
And then he also listed a fewothers that I wanted to mention
Go Down on Low-Code with RobKopolwicz and Ryan Duggan I
should have practiced thosenames A low-code approach, which
we have talked about before.
And then, of course, CRM Rockswith Marcus Ellenson, which have
(43:45):
both been guests on and he'sbeen going, for this has been
his since 2013.
So I mean, it's just a staplepodcast in our community and he
still keeps going.
It's just a staple podcast inour community and he still keeps
going.
It's amazing.
So a bit of shout out to bothJohannes and all the other
podcasts out there that keepeveryone up to date on the
(44:08):
latest news for Power Platform.
So that's very good.
Hello, Code.
Yes.
Nick (44:12):
Cool, all right.
So basically, yeah, I thinkwe're not going to.
I think, in terms of the events, yes, we're.
You know we're going to beparticipating in all those and
that's where you get your rubberduck.
The only one I want to shoutout is, if you're going to
register for the Power PlatformCommunity Conference in Las
Vegas, use BOOST100 to get $100discount to that off your ticket
(44:33):
.
But love to see you there andget your rubber duck from us.
Still have a big box full thatI'll be dragging with me and
yeah, and then our next episode.
We're still trying to adjustfor our summer schedule and
things like that, so we'll stillbe.
I think you just watch thesocials, we'll let you know, but
it will be on a Wednesday,either the 6th of August or the
(44:56):
following week.
At this point we haven't quitesolidified that just because
vacations and summer and youguys got a bonus episode from us
last week, so I don't want tohear any complaints.
Ulrikke (45:06):
I think it's all good.
Have a fantastic rest of yoursummer, guys, and we'll catch
you when we catch you.
Bye-bye, bye.
Nick (45:13):
Thank you for listening.
No-transcript.
Popular Podcasts
Stuff You Should Know
If you've ever wanted to know about champagne, satanism, the Stonewall Uprising, chaos theory, LSD, El Nino, true crime and Rosa Parks, then look no further. Josh and Chuck have you covered.
Crime Junkie
Does hearing about a true crime case always leave you scouring the internet for the truth behind the story? Dive into your next mystery with Crime Junkie. Every Monday, join your host Ashley Flowers as she unravels all the details of infamous and underreported true crime cases with her best friend Brit Prawat. From cold cases to missing persons and heroes in our community who seek justice, Crime Junkie is your destination for theories and stories you won’t hear anywhere else. Whether you're a seasoned true crime enthusiast or new to the genre, you'll find yourself on the edge of your seat awaiting a new episode every Monday. If you can never get enough true crime... Congratulations, you’ve found your people. Follow to join a community of Crime Junkies! Crime Junkie is presented by audiochuck Media Company.
NFL Daily with Gregg Rosenthal
Gregg Rosenthal and a rotating crew of elite NFL Media co-hosts, including Patrick Claybon, Colleen Wolfe, Steve Wyche, Nick Shook and Jourdan Rodrigue of The Athletic get you caught up daily on all the NFL news and analysis you need to be smarter and funnier than your friends.