Setting Autonumber Seed in a Managed Solution in Power Platform

2024-12-052024-12-11 ~ Jonas Rapp ~ Leave a comment

Some details in the Power Platform are intentionally excluded from the solutions. Still, most of us developers think they are part of them—unless we read enough about the docs (which is boooring).
One example is Seed for columns that have the type Autonumber.

As far as I know, the seed is not stored in our tables or columns; it is only known in the deep down of the mystery SQL Server. So, how can it even be settable in the Maker Portal?

Continue reading →

Microsoft Power Fx + XRM Tokens

2022-11-132022-11-13 ~ Jonas Rapp ~ 1 Comment

Why mixing two very different but very similar features?
I hope you will see it, if you read on…

What’s a Token?

I don’t really know why… but it’s a word, a special word, representing other words… where the word is a data word, will be replaced with words from the actual data, as it is actually used. I think.

Continue reading →

Power Apps Studio and GitHub 🚀

2022-01-042022-01-05 ~ Jonas Rapp ~ 6 Comments

During the Christmas holiday, I used my time off to explore the integration between Power Apps and GitHub.

I started to explore this new feature because I wanted to see changes to the code. I mean real code. There is no way to easily see the code… Well, Power Apps is a no/low-code as we know, so I also know we should not want to see code… But I do. I have to.

Continue reading →

Use Power Automate to maintain Top Parent Account in account hierarchies

2020-12-302020-12-31 ~ Jonas Rapp ~ 2 Comments

Using account hierarchies in Microsoft Dataverse (XRM, you know) is super easy with the out of the box Parent Account fishhook relationship.
This article will demonstrate how to maintain information about the Top Parent Account on all accounts, using a single Power Automate cloud flow.

Continue reading →

A Pro Code Escape in Power Automate

2020-09-102020-09-22 ~ Jonas Rapp ~ 5 Comments

Microsoft Power Automate is a fantastic platform when it comes to low-code automation, with connectors to literally hundreds of data sources.
But what if you need to do something too complex for the existing flow actions?
**Take the Pro Code Escape with the Common Data Service.**

Continue reading →

Querying date intervals in the Common Data Service

2020-06-012020-08-21 ~ Jonas Rapp ~ 13 Comments

Querying date intervals in Microsoft Common Data Service, Power Apps and Dynamics 365 is not always possible using Advanced Find nor is it as easy as working with plain SQL.

TL;DR – with FetchXML this is quite possible!

Continue reading →

Conditional Unique Auto Number Sequences in Microsoft Dynamics 365 / CRM

2020-03-052020-08-21 ~ Jonas Rapp ~ 12 Comments

A common request for Auto Numbers in Microsoft Dynamics 365 (CDS/CRM) is to have one number field with different formats and unique sequences based on data on the record or it’s parents.
I call this “Conditional Unique Auto Number Sequences”.

Continue reading →

Avoid nested conditionals in Microsoft Flow by using Guard Conditions

2019-03-222020-08-21 ~ Jonas Rapp ~ 6 Comments

After working as a developer for a quarter century I have seen my fair share of nested conditionals and probably caused way beyond my fair share.
Nested conditionals make the code harder to read and simply less aesthetic.

Continue reading →

Dynamic content in Auto Numbers for Microsoft Dynamics 365 / CRM

2019-02-142020-09-10 ~ Jonas Rapp ~ 10 Comments

As the creator of the Auto Number Manager tool in XrmToolBox, I get two questions more than any other questions:

How can I number existing records?
How can I add dynamic content to the numbers?

In a previous article I gave my solution to the first question. I will now dive into the second one and show a simple way of adding dynamic information from the numbered entity and related entities into the numbered attribute.

Continue reading →

Auto Numbering existing records in Microsoft Dynamics 365 / CRM

2019-02-022020-09-10 ~ Jonas Rapp ~ 23 Comments

As the creator of the Auto Number Manager tool in XrmToolBox, I get two questions more than any other questions:

How can I number existing records?
How can I add dynamic content to the numbers?

To answer these questions once and for all, I will post my suggestions in two articles. I will step way outside my comfort zone of coding the solutions and give you strictly no-code alternatives.
Well, I do feel reasonably comfortable, since I wrote the code in the tools we need… ?

Continue reading →

Category: No-Code

Setting Autonumber Seed in a Managed Solution in Power Platform

Some details in the Power Platform are intentionally excluded from the solutions. Still, most of us developers think they are part of them—unless we read enough about the docs (which is boooring).
One example is Seed for columns that have the type Autonumber.

Like this:

Microsoft Power Fx + XRM Tokens

What’s a Token?

Like this:

Power Apps Studio and GitHub 🚀

Like this:

Use Power Automate to maintain Top Parent Account in account hierarchies

Using account hierarchies in Microsoft Dataverse (XRM, you know) is super easy with the out of the box Parent Account fishhook relationship.
This article will demonstrate how to maintain information about the Top Parent Account on all accounts, using a single Power Automate cloud flow.

Like this:

A Pro Code Escape in Power Automate

Microsoft Power Automate is a fantastic platform when it comes to low-code automation, with connectors to literally hundreds of data sources.
But what if you need to do something too complex for the existing flow actions?
**Take the Pro Code Escape with the Common Data Service.**

Like this:

Querying date intervals in the Common Data Service

Querying date intervals in Microsoft Common Data Service, Power Apps and Dynamics 365 is not always possible using Advanced Find nor is it as easy as working with plain SQL.

TL;DR – with FetchXML this is quite possible!

Like this:

Conditional Unique Auto Number Sequences in Microsoft Dynamics 365 / CRM

A common request for Auto Numbers in Microsoft Dynamics 365 (CDS/CRM) is to have one number field with different formats and unique sequences based on data on the record or it’s parents.
I call this “Conditional Unique Auto Number Sequences”.

Like this:

Avoid nested conditionals in Microsoft Flow by using Guard Conditions

After working as a developer for a quarter century I have seen my fair share of nested conditionals and probably caused way beyond my fair share.
Nested conditionals make the code harder to read and simply less aesthetic.

Like this:

Dynamic content in Auto Numbers for Microsoft Dynamics 365 / CRM

As the creator of the Auto Number Manager tool in XrmToolBox, I get two questions more than any other questions:

Like this:

Auto Numbering existing records in Microsoft Dynamics 365 / CRM

As the creator of the Auto Number Manager tool in XrmToolBox, I get two questions more than any other questions:

Like this:

Some details in the Power Platform are intentionally excluded from the solutions. Still, most of us developers think they are part of them—unless we read enough about the docs (which is boooring).One example is Seed for columns that have the type Autonumber.

Share this:

Like this:

What’s a Token?

Share this:

Like this:

Share this:

Like this:

Using account hierarchies in Microsoft Dataverse (XRM, you know) is super easy with the out of the box Parent Account fishhook relationship.This article will demonstrate how to maintain information about the Top Parent Account on all accounts, using a single Power Automate cloud flow.

Share this:

Like this:

Microsoft Power Automate is a fantastic platform when it comes to low-code automation, with connectors to literally hundreds of data sources.But what if you need to do something too complex for the existing flow actions?Take the Pro Code Escape with the Common Data Service.

Share this:

Like this:

Querying date intervals in Microsoft Common Data Service, Power Apps and Dynamics 365 is not always possible using Advanced Find nor is it as easy as working with plain SQL.

TL;DR – with FetchXML this is quite possible!

Share this:

Like this:

A common request for Auto Numbers in Microsoft Dynamics 365 (CDS/CRM) is to have one number field with different formats and unique sequences based on data on the record or it’s parents.I call this “Conditional Unique Auto Number Sequences”.

Share this:

Like this:

After working as a developer for a quarter century I have seen my fair share of nested conditionals and probably caused way beyond my fair share.Nested conditionals make the code harder to read and simply less aesthetic.

Share this:

Like this:

As the creator of the Auto Number Manager tool in XrmToolBox, I get two questions more than any other questions:

Share this:

Like this:

As the creator of the Auto Number Manager tool in XrmToolBox, I get two questions more than any other questions:

Share this:

Like this:

Some details in the Power Platform are intentionally excluded from the solutions. Still, most of us developers think they are part of them—unless we read enough about the docs (which is boooring).
One example is Seed for columns that have the type Autonumber.

Using account hierarchies in Microsoft Dataverse (XRM, you know) is super easy with the out of the box Parent Account fishhook relationship.
This article will demonstrate how to maintain information about the Top Parent Account on all accounts, using a single Power Automate cloud flow.

Microsoft Power Automate is a fantastic platform when it comes to low-code automation, with connectors to literally hundreds of data sources.
But what if you need to do something too complex for the existing flow actions?
**Take the Pro Code Escape with the Common Data Service.**

A common request for Auto Numbers in Microsoft Dynamics 365 (CDS/CRM) is to have one number field with different formats and unique sequences based on data on the record or it’s parents.
I call this “Conditional Unique Auto Number Sequences”.

After working as a developer for a quarter century I have seen my fair share of nested conditionals and probably caused way beyond my fair share.
Nested conditionals make the code harder to read and simply less aesthetic.