Guides

The planning assistant finds available resources that actually match the requirements of the assignment, instead of requiring the planner to search through the schedule board manually. It does not make the decision—but it eliminates options that are not feasible anyway.

A real-time dashboard should support decision-making throughout the day, not summarize the month. This places different demands on what is displayed.

Data quality deteriorates on its own. A small, regular routine beats a major clean-up every other year.

Connecting a new source to customer profiles is mostly about mapping and involves very little clicking. This guide shows the sequence of steps that ensures the connection actually produces the correct profiles.

Tracking done incorrectly leaves you with a CRM full of emails no one can find again. This guide shows you the habit that makes the history useful.

A good review takes an hour and results in concrete actions. A bad one is a recitation of figures everyone has already seen.

A canvas app is the fastest way to turn a spreadsheet into something that works on mobile. This guide walks you through a simple app and the choices that determine whether people will use it.

A business process flow gives salespeople a consistent way of working. This guide shows you how to set up one that actually gets used.

The run history shows exactly where and why a flow stopped. This guide outlines the sequence that will help you find the cause fastest.

Dataverse storage is not free, and usage grows quietly. Here’s what takes up space and what you can do about it.

ProsessPilotenes testing is based on ISO/IEC 29119, with three main strategies suited to different parts of a delivery. Use this approach when determining the testing strategy for a delivery, normally as early as the sales phase.

Tasks are the simplest type of entry there is, and the one that matters most for ensuring that nothing falls through the cracks.

The work order is the starting point for everything else in Field Service. It can be created manually, but in practice, most work orders originate from a case, a preventive maintenance agreement, or a sale. Here is how to create one manually—and what you should enter to ensure that scheduling works properly afterward.

The equipment register forms the basis for service agreements and service history. This guide shows you how to set it up without drowning in data.

Consent is both a legal requirement and essential for ensuring that your messages are delivered. This guide shows you how to record consent in a traceable way and make unsubscribing painless.

The audit log shows who changed what and when. It uses storage, so it should be enabled with care.

For the App for Outlook to appear, three things must be in place: a license, a security role, and an approved mailbox. This guide takes you through them in the correct order.

A good estimate for a DevOps task requires considering several factors, not just the development time itself. Use this approach when creating a new task, and always involve the person who will carry out the work.

Skills-based routing requires that skills are registered and kept up to date. Here is the setup and the pitfall that causes inquiries to remain unassigned.

An import model shows old figures until someone updates it. Scheduled updates do this automatically—once the prerequisites are in place.