Welcome to the kitchen
Power Platform recipes that hold up outside the demo
I am Sebastian. I build Dynamics 365 and Power Platform solutions for a living and write down the ones that survived production — including the parts that burned first.
The menu
Pick a section of the kitchen
Fresh from the kitchen
Most recently plated up
Two cooks, one pot: rebuilding a double opt-in
Read Two cooks, one pot: rebuilding a double opt-inWhat nobody tells you about the marketing form editor
Read What nobody tells you about the marketing form editorThe three-layer consent hierarchy in Customer Insights - Journeys
Read The three-layer consent hierarchy in Customer Insights - JourneysFrom the pass
Low-code until it isn't
Most of what I write about starts in the maker portal and ends in a script, a plugin or a custom API — because that is where the awkward requirements actually get solved. Recipes here show both halves, not just the clickable one.
Recipes with code in them// Method: cream the purposes first, then fold in the
// topics. Add both at once and the mixture splits.
const REST = 150; // ms. not in any recipe book
function prefill(consents) {
const blocks = document.querySelectorAll(".consentBlock");
creamPurposes(blocks, consents);
setTimeout(() => foldInTopics(blocks, consents), REST);
}
function isTopic(block) {
// looks like a value, is a string
const id = block.dataset.topicid;
return id && id !== "undefined";
}
function serve(cb) { // plating is not cooking
cb.checked = true;
for (const e of ["input", "change"])
cb.dispatchEvent(new Event(e, { bubbles: true }));
}
The cook
Koch is German for cook
Industrial engineer by training, Power Platform consultant by trade, generalist by nature. Based in Munich, deepest in Customer Insights - Journeys and consent.
Read the longer versionNew recipes, whenever one is actually done
No schedule, no filler. A post goes up when something has been built, tested and is worth passing on.