
How two departments agree on one number and keep agreeing
Two correct figures for the same measure differ on timing, population or attribution. Find which one, write the definition down, then name an owner.
Evergreen collection
Practical patterns for architecture, low-code governance, automation, and the systems that connect them.

Two correct figures for the same measure differ on timing, population or attribution. Find which one, write the definition down, then name an owner.

Content assignment decides what a user sees, authorisation decides what runs, and the two drift apart unless you design roles around the job.

Subsidiaries should track legal entity structure, not divisions. Settle the hierarchy, base currency and access design before the first transaction posts.

A flow that stops is visible in run history. A flow that half-finishes leaves two systems disagreeing, so design the handlers, retries and owner first.

Most CMDBs are partly wrong, and the workarounds cost more than the errors. Where the effort pays: identification, relationships, precedence, retirement.

Route every step to a security group rather than a person, delete the approvals nobody has ever rejected, and let conditions skip the rest.

Function access decides what someone can do. The security profile decides whose records they do it to. Most Fusion HCM exposures live in that gap.

A query your data source cannot evaluate still returns an answer, built from part of the table, and sample data will never show you the gap.

Preview status belongs to the instance rather than a setting, so the sandbox you test a seasonal release in has to be planned months before the notes land.

Decide what moves before you touch a mapping rule, read the merge output yourself, and verify against totals the business already argues about.

Most slow NetSuite saved searches read far more than anyone needs and throw it away. Fix the date bound and the filter placement first.

A portal is fast on an administrator's laptop and slow on a customer's phone. Fix permission scope, list design and image weight before launch.

A permission role says what may be done and a group says who does it. The assignment binds granters to a target population, and that pairing is where access breaks.

Model queues on kinds of work, pin down the order your assignment rules evaluate in, and give every request that matches nothing a queue someone opens daily.

A Power BI import carries everything the refresh account could read. Rebuild the row filters, maintain the mapping table, and test as a restricted user.

Build where the work persists, rehearse the promotion, version every build, and decide who can switch the app off before anyone needs to.

Scope, identity and a realistic approval step decide whether a Fusion agent rollout stays reviewable. Capture the baseline and the off switch first.

A table permission granted for one page applies everywhere that table can be reached. Check the whole surface before a Power Pages site faces the internet.

Capacity, priority and presence decide how Omni-Channel behaves at peak. Set them from real numbers, then test with two agents and one saturated queue.

An account hierarchy records a commercial relationship. Case visibility is a separate decision, and the hierarchy setting is the one that leaks a child's cases.

Integration Center handles a scheduled extract well. The entity you pick, the as of date and the failure email decide whether anyone can trust the file.

Most slow Workday reports retrieve far more than the question needs and then discard it. Fix the data source and the filters before you touch the columns.

The scripts and business rules inside your instance outlive whoever wrote them. Record why the logic exists, keep it in one place, and fail loudly.

Most Dataverse growth comes from attachments, audit rows, trace logs and environments nobody deleted. The per-table view in the admin center names yours.

One clean parallel cycle proves very little. Build the cases that break payroll into the run, then triage every variance before anyone signs.

A true-up notice is a commercial conversation with a deadline attached. Reproduce the vendor count yourself before you agree to any of it.

Phase one lands or stalls on four calls made before build: real scope, named data owners, whether the CMDB is in, and a counted integration list.

When finance is too small to split creating a vendor from paying one, pick the two conflicts that carry the money and mitigate them in writing.

Writing the two week handover runbook exposes every job only you can run, and the page telling your stand-in what not to attempt is the one that saves you.

People describe the documented path when their manager is in the room. The real process lives in the exceptions, and you have to go looking for it.

Most mock loads are built to pass. A rehearsal proves something only at full volume, on the real cutover clock, with the awkward records left in.

Hypercare catches the loud failures. Notification rules that never fire, one-person assignment groups and SLA clocks on the wrong schedule wait for week two.

Dataverse gives you a relational model, row and column security, and rules that hold whoever wrote the record. A five person spreadsheet needs none of it.

Plenty of Dataverse walls are a training or licensing problem. Pay for outside help when the model, the security map, or the scale is beyond your team.

Agentforce agents are handed a job rather than a script, bounded by topics and instructions, and they see exactly what the user they run as can see.

Fusion Cloud is several application families sharing one platform, so saying you run Fusion tells nobody which ones you actually bought.

SAP BTP is one name over four different things: extension runtimes, integration, data services and AI. Knowing which one you mean is most of the answer.

ServiceNow's ITSM products are applications on a platform. App Engine lets you build your own there, inheriting the workflow, approvals and catalog you already run.

Workday gives you no general purpose database. Extend is the sanctioned way to build something custom inside the tenant's own security, worker data and approvals.

How to find the Fusion Cloud ERP modules and user licenses nobody actually touches, and turn that into a renewal position.

A reorg breaks employee feeds that were built against last year's org chart. Pick keys and reconciliation that outlive the chart.

Three tenure calculations, three headcount numbers, one leadership meeting. A method for auditing Workday calculated field sprawl before reports time out.

A working method for auditing Salesforce profiles and permission sets, and removing the access you find without breaking someone's Monday.

Most CABs read thirty changes aloud and approve them in forty minutes. Here is a method that puts the meeting's attention on the two that could hurt you.

A practical method for keeping ServiceNow access requests auditable long after the project that justified them ends.

A first-person audit method for finding duplicate Workday security groups, tracing mystery access back to its origin, and setting a review cadence that sticks.

Oracle and SAP both ship bundles where nearly every entry claims top severity. Here is the four-question order I actually use to triage them for real.

Before a three-year SaaS renewal call, pull your own usage data, read the vendor timeline pressure for what it is, and decide what discount is worth the lock-in.

A practical method for catching Workday comp cycle configuration drift before go-live, built around an approval step that quietly survives the manager it was written for.

A full governance program takes years to fund. Material and vendor master ownership is where an S/4HANA team can start this quarter.

A working rule for deciding which Power Platform solutions get their own dev, test, and production environments, and who approves promotion between them.

Workday Extend apps read HCM data by default. Decide who reviews access, who tests against real data, and who owns the app before it ships.

A pipeline survives when the build takes under two minutes, test data looks real, and a maker can roll back without opening a ticket.

A migration statement of work only holds up if it names a discovery gate, a rehearsed change order, and a written data assumption.

A fifteen-minute conversation before the first screen is built, recorded on the Dataverse solution, does more than an approval form completed after go-live.

The four numbers a platform owner needs before a Power Platform, Dynamics 365, or Agentforce repackaging note gets forwarded to finance.

Name the business event, send only fields the receiver acts on, version when meaning changes, and write down what happens to duplicates.

Power BI can only answer what the Dataverse model was built to hold. Write the leader's questions first, with the decision, grain, and freshness each needs.

Before a Copilot Studio or Agentforce pilot gets more users, check it has four named owners, a visible failure path, and a review date.

An agent assessing change impact trusts every CI and relationship it finds. Fix class ownership and identification rules before it goes live.

Match on the number the business already reads out, enforce it as a unique field on both sides, and test the missing, repeated, and near-twin key first.

When a shared Power Automate flow fails, find the work that stopped, name one lead, and write the ServiceNow record before anyone resubmits a run.

Send the script early, load your own duplicates and odd legal entities, and ask to see a failure. A CRM demo only counts as evidence when you run it.

The questions a platform team should ask before a shared Power Platform solution reaches other makers, and where to keep the answers for the next owner.

A center of excellence earns its keep with office hours and a pattern library, and loses it the day it starts approving every app or owning every maker's flow.