reenhanced

Tag: site map

  • Model-driven apps in PowerApps: Site Map

    Model-driven apps in PowerApps: Site Map

    Welcome to the third article in the model-driven app series! Today we will look at the Site Map and understand how it works from the back end / system administrator view and how that translates to the front end / end user view. This series includes six articles that will help you to get to know and use model-driven apps and PowerApps:

    Site Map

    This is the single most important component of your model-driven app. It controls which areas of Dynamics 365 are accessible in your App. When building your app, you will have two options when it comes to a site map:

    1. Use existing (from a solution)
    2. Create new

    Your map consists of three components:

    1. Area
    2. Group
    3. Subarea

    Let’s first look at these three components from the back end view for System Administrators and app builders:

    Site map back end
    The site map from the build perspective

    Utilizing a simple drag and drop interface (similar to what you see when building Business Rules and Business Process Flows), you can add new Areas, Groups and Subareas to your Sitemap Designer. But what do these mean to the end user? What is the difference between the three components and how do they display?

    To best understand the difference between an area, group and subarea on the Sitemap Designer, let’s take a look at the end user / front end view of the sitemap:

    Site map, front end
    The site map from the end user perspective

    Take a look at the image above to understand how the site map displays to users. The table below will explain how the highlighted colors relate to the Sitemap Designer.

    Highlight colorSitemap Designer Detail
    BlueArea
    GreenGroup
    YellowSubarea

    Now that you understand what each component is, build out your app’s sitemap. Once you have completed the build, make sure to Save it by clicking the Save icon in the top right-hand corner of the Sitemap Designer. Next, click Publish.

    After your site map has been saved and published, it’s time to move on to the fun stuff – adding components and setting properties. Stay tuned for the next article in our series, where we dive into components (entities, dashboards, business process flows and more)!

    Need Help?

    Do you need help planning your Site Map? Feel free to reach out to reenhanced! Fill out our Contact Form with details about what you’re working on, or email me directly at heidi@reenhanced.com. Happy building!

  • Model-driven apps in PowerApps: Using the App Designer

    Model-driven apps in PowerApps: Using the App Designer

    Welcome to our second blog in the model-driven app series! Today we will focus on getting to know the App Designer. This series includes six articles that will help you to get to know and use model-driven apps and PowerApps:

    A blank canvas to build your model-driven app!

    When you open your model-driven App in the App Designer, it will resemble the image above. You will notice a few main areas here:

    • Site Map
    • Dashboards
    • Components (Artifacts & Entity Assets)
    • Properties

    Using the App Designer is fairly simple and should be familiar to System Administrators as it uses a similar drag and drop configuration style used in building business rules and business process flows. Microsoft has done an excellent job making configurations like these accessible to the less technical System Administrator (like yours truly!).

    Let’s briefly look at each of these – as all of these areas will be covered thoroughly in subsequent articles.

    App Designer Areas
    Site MapControls which areas of Dynamics 365 can be accessed in this App
    DashboardsList of any system dashboard included in the App
    ComponentsA list of entities and entity assets (forms, views, charts) that are in this App
    PropertiesName and description of the App, custom icon (optional), unified interface URL

    Stay tuned for the rest of this series on building a model-driven app in Dynamics 365 using PowerApps, where we will dive deeper into the Site Map, Components and Properties.