從 Common Data Service 建立應用程式Creating an app from the Common Data Service

從 Common Data Service 產生包含三個畫面的應用程式,然後從應用程式探索畫面和控制項。Generate a three screen app from the Common Data Service, then explore screens and controls from the app. 更新應用程式畫面、控制項和欄位:從應用程式納入其他資料並觸發流程。Update app screens, controls, and fields; bring in additional data and trigger a flow from the app.

您將學到如何...

產生應用程式Generate an app

在這一節的課程中,我們將根據 Common Data Service 中的實體建立應用程式。In this section of the course, we'll create an app based on entities in the Common Data Service. 實體是共用資料的區塊,可修改、儲存、擷取並與之互動。Entities are chunks of shared data that can be modified, stored, retrieved, and interacted with. 我們將從實體產生應用程式、示範如何自訂應用程式、新增其他資料來源,以及從應用程式呼叫流程。We'll generate the app from an entity, show you how to customize the app, add another data source, and call a flow from the app. 如果您已完成從 SharePoint 清單建立應用程式的這一節,我們將涵蓋一些相同的領域但是更為深入探討,尤其是有關自訂應用程式。If you already completed the section on creating an app from a SharePoint list, we will cover some of the same territory but in more depth, especially around customizing the app.

我們將建立案例管理應用程式,IT 部門可以用來追蹤、設定優先順序,以及處理整個組織的硬體和軟體問題。We'll create a case-management app that an IT department could use to track, prioritize, and act on hardware and software issues across an organization. 當您瀏覽主題時,您也可以想想這類應用程式的其他用途。As you go through the topics, you might also think of other uses for an app like this. 我們使用 Common Data Service 中的資料,因為它非常適合儲存應用程式資料,但您也可以使用不同的資料來源建置相同的應用程式。We're using data from the Common Data Service because it's well-suited to storing app data, but you could build the same app with a different data source.

PowerApps 包含更複雜的案例管理範本,其使用與我們將建置之應用程式相同的實體。PowerApps includes a more complex Case Management template that uses the same entities as the app we'll build. 完成此節之後,我們鼓勵您瀏覽該範本,以了解您可以在 PowerApps 中建置的實體。After you've completed this section, we encourage you to explore that template to get a sense of what you can build in PowerApps.

建立 Common Data Service 資料庫Create a Common Data Service database

如果您還沒有資料庫的話,建置此應用程式的第一步就是建立 Common Service 資料庫。The first step in building this app is to create a Common Service database if you don't already have one. 您可在「環境」中建立 Common Data Service 資料庫。You create a Common Data Service database in an environment. 環境是應用程式和其他資源的容器 (您將在本課程的稍後進一步了解環境)。An environment is a container for apps and other resources (you'll learn more about environments later in the course). 環境系統管理員可以依照下列步驟來建立資料庫 (如果您不是系統管理員,請洽詢您組織中的系統管理員)。An environment admin can follow these steps to create a database (if you're not an admin, check with an admin in your organization).

首頁 索引標籤,按一下 [建立資料庫]。From the Home tab, click Create Database.

建立 Common Data Service 資料庫

指定您是否要限制資料庫存取 (我們會保持開啟),然後按一下 [建立我的資料庫]。Specify whether you want to restrict access to the database (we'll keep it open), then click Create my database.

指定 Common Data Service 存取權

當處理序完成時,您會看到常見資料模型中包含的所有標準實體。When the process is complete, you see all the standard entities that are included in the common data model. 其中部分實體如下所示。Some of them are shown below.

Common Data Service 標準實體

從案例實體產生應用程式Generate an app from the Case entity

資料庫建立完畢後,我們可以連接到案例實體並產生應用程式。Now that the database is created, we connect to the Case entity and generate an app. 按一下 [新增應用程式],然後 [PowerApps Studio for web]。Click New app, then PowerApps Studio for web.

在 PowerApps Studio for web 中新增應用程式

我們要建置 Common Data Service 實體的電話應用程式,因此在 [Common Data Service] 下按一下或點選 [電話配置]。We're building a phone app for a Common Data Service entity, so under Common Data Service click or tap Phone layout.

Common Data Service 的電話應用程式

在下一個畫面中,選擇連接以及要連接的實體,然後按一下 [連接]。In the next screen, you choose a connection and an entity to connect to, then click Connect.

連接到案例實體

按一下 [連接] 之後,PowerApps 會開始產生應用程式。After you click Connect, PowerApps starts to generate the app. PowerApps 會進行各種資料推斷,因而產生有用的應用程式做為起點。PowerApps makes all sorts of inferences about your data so that it generates a useful app as a starting point.

在 PowerApps Studio 中檢視應用程式View the app in PowerApps Studio

隨即在 PowerApps Studio 中開啟新的應用程式 (包含三個畫面)。Your new three-screen app opens in PowerApps Studio. 從資料產生的所有應用程式都具有相同的畫面組合︰All apps generated from data have the same set of screens:

  • 瀏覽 畫面︰您可以在其中瀏覽、排序、篩選和重新整理從清單中提取的資料,以及藉由按一下 (+) 圖示來新增項目。The browse screen: where you browse, sort, filter, and refresh the data pulled in from the list, as well as add items by clicking the (+) icon.
  • 詳細資料 畫面︰您可以在其中檢視更詳細的項目資訊,並可選擇刪除或編輯項目。The details screen: where you view more detail about an item, and can choose to delete or edit the item.
  • 編輯/建立 畫面︰您可以在其中編輯現有的項目或建立新的項目。The edit/create screen: where you edit an existing item or create a new one.

在左側的導覽列中按一下或點選右上角的圖示,切換至縮圖檢視。In the left navigation bar, click or tap an icon in the upper-right corner to switch to the thumbnail view.

切換檢視

按一下或點選每個縮圖,以檢視該畫面上的控制項。Click or tap each thumbnail to view the controls on that screen.

產生的應用程式

接下來,我們會更進一步探索應用程式,而後再自訂應用程式,使其更符合我們的需求。Next we'll explore the app in more detail and then customize it to better suit our needs.

探索產生的應用程式Explore a generated app

在本主題中,我們會更仔細查看產生的應用程式 - 檢閱可定義應用程式行為的畫面和控制項。In this topic, we look more closely at the generated app - reviewing the screens and controls that define the app's behavior. 我們不會講解所有細節,但是看到有關此應用程式運作方式的詳細資訊,將可協助您建置自己的應用程式。We won't go through all the details, but seeing more about how this app works will help you to build your own apps. 在稍後的主題中,我們將探討與畫面和控制項搭配使用的公式。In a later topic, we'll look at the formulas that work with screens and controls.

在預覽模式中執行應用程式Run the app in preview mode

按一下或點選Click or tap 啟動右上方的應用程式預覽箭號 以執行應用程式。in the top right to run the app. 如果您瀏覽此應用程式,您會看到它包含實體中的資料,並提供美好的預設體驗。If you navigate through the app, you see that it includes data from the entity and provides a good default experience.

在預覽模式中執行應用程式

了解 PowerApps 中的控制項Understanding controls in PowerApps

控制項只是一個 UI 項目,並有與其相關聯的行為。A control is simply a UI element that has behaviors associated with it. PowerApps 中的許多控制項與您在其他應用程式使用的控制項相同︰標籤、文字輸入方塊、下拉式清單、導覽元素等等。Many controls in PowerApps are the same as controls that you've used in other apps: labels, text-input boxes, drop-down lists, navigation elements, and so on. 但是 PowerApps 具有更特製化的控制項,如資源庫 (顯示摘要資料) 和表單 (顯示詳細資料,讓您能夠建立和編輯項目)。But PowerApps has more specialized controls like Galleries (which display summary data) and Forms (which display detail data and enable you to create and edit items). 此外也有其他很酷的控制項,例如映像相機條碼And also some other really cool controls like Image, Camera, and Barcode. 若要查看可用的控制項,請按一下或點選功能區上的 [插入],然後依序按一下或點選每個選項,從 [文字] 到 [圖示]。To see what's available, click or tap Insert on the ribbon, and then click or tap each of the options in turn, Text through Icons.

PowerApps Studio 功能區上的控制項索引標籤

探索瀏覽畫面Explore the browse screen

三個應用程式畫面都有主控制項和一些額外的控制項。Each of the three app screens has a main control and some additional controls. 應用程式中的第一個畫面是瀏覽畫面,預設名稱為 BrowseScreen1The first screen in the app is the browse screen, named BrowseScreen1 by default. 在此畫面上的主控制項是名為 BrowseGallery1 的資源庫。The main control on this screen is a gallery named BrowseGallery1. BrowseGallery1 包含其他控制項,例如 NextArrow1 (圖示控制項 - 按一下或點選以移至詳細資料畫面)。BrowseGallery1 contains other controls, like NextArrow1 (an icon control - click or tap it to go to the details screen). 在畫面上也有不同的控制項,例如 IconNewItem1 (圖示控制項 - 按一下或點選以在編輯/建立畫面中建立項目)。There are also separate controls on the screen, like IconNewItem1 (an icon control - click or tap it to create an item in the edit/create screen).

具有控制項的瀏覽畫面

PowerApps 有各種不同的資源庫類型,因此您可以使用最適合您應用程式配置需求的資源庫。PowerApps has a variety of gallery types so you can use the one that best suits your app's layout requirements. 您稍後會在本節中看到更多控制項配置的方法。You will see more ways to control layout later in this section.

PowerApps 資源庫選項

探索詳細資料畫面Explore the details screen

接下來是詳細資料畫面,預設名稱為 DetailScreen1Next is the details screen, named DetailScreen1 by default. 在此畫面上的主控制項是名為 DetailForm1 的顯示表單。The main control on this screen is a display form named DetailForm1. DetailForm1 包含其他控制項,例如 DataCard1 (卡片控制項,在此情況下顯示問題類型)。DetailForm1 contains other controls, like DataCard1 (a card control, which displays the question category in this case). 在畫面上也有不同的控制項,例如 IconEdit1 (圖示控制項 - 按一下或點選以在編輯/建立畫面中編輯目前項目)。There are also separate controls on the screen like IconEdit1 (an icon control - click or tap it to edit the current item on the edit/create screen).

具有控制項的詳細資料畫面

資源庫的選項有很多,但表單較為直接,不是編輯表單就是顯示表單。There are lots of gallery options, but forms are more straightforward - it's either an edit form or a display form.

PowerApps 表單選項

探索編輯/建立畫面Explore the edit/create screen

應用程式中的第三個畫面是編輯/建立畫面,預設名稱為 EditScreen1The third screen in the app is the edit/create screen, named EditScreen1 by default. 在此畫面上的主控制項是名為 EditForm1 的編輯表單。The main control on this screen is an edit form named EditForm1. EditForm1 包含其他控制項,例如 DataCard8 (卡片控制項,可讓您在此情況下編輯問題類型)。EditForm1 contains other controls, like DataCard8 (a card control, which allows you to edit the question category in this case). 在畫面上也有不同的控制項,例如 IconAccept1 (圖示控制項 - 按一下或點選以在編輯/建立畫面中儲存變更)。There are also separate controls on the screen like IconAccept1 (an icon control - click or tap it to save the changes you made on the edit/create screen).

具有控制項的編輯畫面

現在您已了解應用程式是如何由畫面和控制項所組成,我們將在下一個主題中探討您要如何自訂應用程式。Now that you have a sense of how the app is composed of screens and controls, we'll look at how you customize the app in the next topic.

自訂應用程式Customize the app

在本節中的前兩個主題,您已從 Common Data Service 實體產生應用程式,並探索該應用程式以深入了解三個畫面應用程式是如何組成。In the first two topics in this section, you generated an app from a Common Data Service entity and explored the app to get a better understanding of how three screen apps are composed. PowerApps 產生的應用程式非常有用,但您通常會在應用程式產生後進行自訂。The app that PowerApps generated is useful, but you will often customize an app after it's generated. 在本主題中,我們將逐步討論應用程式瀏覽畫面的一些變更。In this topic, we'll walk through some changes for the browse screen of the app. 您可以自訂任何畫面,但我們要專注於其中一個,並對自訂項目提供深入的探討。You can customize any of the screens, but we wanted to focus on one and provide a bit more depth to the customizations. 我們鼓勵您使用從實體、Excel 檔案或其他來源產生的任何應用程式,並看看您要如何自訂。We encourage you to take any app you generate - from an entity, an Excel file, or another source - and see how you can customize it. 這真的是了解應用程式如何組合的最佳方式。It really is the best way to learn how apps are put together.

當 PowerApps 產生應用程式時,它會決定要使用的版面配置,和要在每個螢幕上顯示的特定欄位。When PowerApps generated the app, it decided on a layout to use, and particular fields to show on each screen. 針對此應用程式,選擇有狀態列的資源庫控制項 (我們很快就會自訂狀態列)。For this app, let's choose a gallery control that has a status bar (we'll customize the status bar shortly). 在右側窗格的版面配置索引標籤上,選取您要的版面配置。In the right-hand pane, on the Layout tab, select the layout you want. 您馬上就能看到結果,因為 PowerApps 在您進行變更時就更新了應用程式。You see the results right away because PowerApps updates the app as you make changes.

變更瀏覽畫面版面配置

有了正確的基本版面配置,現在變更所顯示的欄位。With the right basic layout, now change the fields that are displayed. 按一下或點選第一個項目中的欄位,然後在右側窗格中,變更顯示每個項目的資料。Click or tap a field in the first item, then in the right-hand pane, change the data that is displayed for each item. 這對實體中的每個項目提供了較佳的摘要。This provides a better summary of each item in the entity.

變更瀏覽畫面欄位

變更應用程式主題Change the app theme

PowerApps 提供一組您可以在應用程式中使用的主題,這非常類似 PowerPoint。PowerApps provides a set of themes you can use in your app, much like PowerPoint. 在下列螢幕畫面中,您會看到已套用的沙丘佈景主題,以及我們貼上至應用程式的簡單標誌。In the following screen, you see the Dune theme applied, and a simple logo that we pasted into the app. 這些是基本的變更,但可以大幅改善應用程式的外觀。These are basic changes, but can do a lot to improve the appearance of your app.

變更主題以及新增標誌

使用公式來顯示案例的狀態Use a formula to show the case status

PowerApps 的最大的好處之一,就是不必撰寫傳統的應用程式碼,您不必身為開發人員也可建立應用程式!One of the major benefits of PowerApps is not having to write traditional application code - you don’t have to be a developer to create apps! 但是您仍然需要一種方法來表示應用程式中的邏輯,以及控制應用程式的瀏覽、篩選、排序和其他功能。But you still need a way to express logic in an app and to control an app’s navigation, filtering, sorting, and other functionality. 這就是公式出場的時機。This is where formulas come in.

如果您使用過 Excel 公式,應該不陌生 PowerApps 採用的方法。If you have used Excel formulas, the approach that PowerApps takes should feel familiar. 假設您想要讓狀態列以綠色來表示案例已解決,或以紅色表示相反。Suppose you want to show the status bar in green if a case is resolved, or in red otherwise. 若要這樣做,請在畫面上選取狀態控制項,並接著在公式列中將該控制項的填滿屬性設定為此公式︰If(Status="Resolved", Color.Green, Color.Red)To do this, you select the status control on the screen, and then set the Fill property of that control to this formula in the formula bar: If(Status="Resolved", Color.Green, Color.Red). 這就像是 Excel 的公式,但是 PowerApps 公式參考控制項和其他應用程式項目,而非試算表中的資料格。This is like an Excel formula, but PowerApps formulas refer to controls and other app elements rather than cells in a spreadsheet. 下圖顯示設定公式的位置,以及在應用程式中的結果。The following image shows where to set the formula, and the result in the app.

顯示案例狀態的公式

根據日期排序和篩選Sort and filter based on date

在瀏覽畫面中,產生的應用程式可讓您搜尋案例,並排序資源庫中的項目清單。On the browse screen, the generated app lets you search for cases and sort the list of items in the gallery. 我們要移除搜尋和排序功能,如此有利於根據日期顯示案例。We're going to remove the search and sort functionality in favor of showing cases based on a date. 您可以結合這些方法,但針對此應用程式,我們將著重於以日期為基礎的方法。You could combine these methods, but we'll focus on the date-based approach for this app. 在下圖中,您會看到我們所新增的項目︰In the image below, you see the items we added:

  • 文字標籤 (「顯示之後的案例:」) 讓使用者知道該做什麼︰插入 > 文字 > 標籤;將填滿公式變更為白色A text label ("Show cases after:") so users know what to do: Insert > Text > Label; change the Fill formula to White.
  • 日期選擇器︰插入 > 控制項 > 日期選擇器A date picker: Insert > Controls > Date picker.
  • 將瀏覽資源庫項目屬性連接至日期選擇器的公式︰Filter(Case, DatePicker1.SelectedDate < LastModifiedDateTime)A formula that connects the browse gallery Items property to the date picker: Filter(Case, DatePicker1.SelectedDate < LastModifiedDateTime).

日期會設定為 10 月 20 日,您看到的結果是應用程式會顯示在此日期之後建立的案例。The date is set to Oct 20 and you see the result that the app is showing the cases created after this date. 請注意,根據預設,在實體中的所有案例會具有相同的上次修改日期。Note that by default, all cases in the entity have the same last modified date. 您可以更新其中一或多個案例,以查看篩選的運作方式。You can update one or more to see how filtering works. 我們在稍後的課程將討論使用實體資料。We cover working with entity data later in the course.

更新應用程式以使用資料選擇器

顯示案例總數Show total number of cases

我們目前涵蓋的範圍甚廣,但是我們就快完成自訂了。We're covering a lot of ground here, but we're almost done with the customizations. 在本主題中,我們會做的最後一件事是新增顯示兩個數字的標籤︰案例的總數,以及符合以日期為基礎篩選條件的案例數目。The last thing we'll do in this topic is add labels that show two numbers: the total number of cases and the number of cases that match our date-based filter.

顯示總數和篩選的案例

影片將詳述如何新增這兩個標籤,但以下屬性是我們為每個標籤設定的基本概念︰The video goes into detail about how to add the two labels, but here's the basics on which properties we set for each label:

  • 對齊 = CenterAlign = Center
  • 寬度 = Parent.Width/2Width = Parent.Width/2
  • 左側方塊文字 = "Total cases: " & CountRows(Case)Left box Text = "Total cases: " & CountRows(Case). 這包括實體中的所有案例。This includes all cases that are in the entity.
  • 右側方塊文字 = Filtered cases: " & CountRows(BrowseGallery1.AllItems)Right box Text = Filtered cases: " & CountRows(BrowseGallery1.AllItems). 這僅包括符合以日期為基礎篩選條件的案例。This includes only those cases that match the date-based filter.

好的,這是應用程式自訂項目的總結,在下一個主題中,我們將新增資料來源以及流程,並且展示完成的應用程式。OK, that wraps up the app customizations - in the next topic we'll add a data source, and a flow, and show you the finished app.

新增資料來源和流程Add a data source and flow

到目前為止,在本節中我們已經產生了以 Common Data Service 案例實體為基礎的應用程式、探索應用程式如何組合,並且以數種方式自訂應用程式。So far in this section, we have generated an app based on the Case entity from the Common Data Service, explored the app to see how it's put together, and customized the app in several ways. 在本節中的最後一個主題中,我們將介紹另一個標準實體,並使用 Microsoft Flow 來傳送電子郵件。In the final topic for this section, we will bring in another standard entity, and use Microsoft Flow to send an email. 應用程式將會觸發流程,如此當案例更新時,開啟案例的人員便會收到通知。The app will trigger a flow so that the person who opened a case is notified when the case is updated. 我們即將完成本主題中的特定案例,但您學習的技巧可適用於許多種類的應用程式。We're completing a particular scenario in this topic, but the skills you learn are applicable across many kinds of apps. 開始使用實體吧。Let's get started with the entities.

檢閱實體關聯性Review entity relationships

我們很快將要新增連絡人實體,但我們首先要探討案例和連絡人實體是如何互相關聯的。We'll add the Contact entity shortly, but first we'll look at how the Case and Contact entities relate to each other. 在案例實體中,您會看到其中一個欄位是 CurrentContact,資料類型為查閱In the Case entity, you see that one of the fields is CurrentContact, with a data type of Lookup. 這表示這個欄位與另一個資料表具有關聯性。This means that this field is used in a relationship with another table.

案例實體欄位

關聯性索引標籤上,您看到相關的實體是連絡人On the Relationships tab, you see that the related entity is Contact. 請記住這點,因為我們在本主題稍後將使用此關聯性。Keep that in mind because we will use this relationship later in this topic.

案例實體關聯性

將實體新增至應用程式Add an entity to the app

在 PowerApps 中新增資料來源很簡單。Adding a data source in PowerApps is straightforward. 在右側窗格中,按一下或點選 [資料來源],然後 [新增資料來源]。In the right-hand pane, click or tap Data sources, then Add data source. 在此情況下,接著選擇 [Common Data Service] 連接,然後選取 [連絡人] 實體。In this case, then choose the Common Data Service connection and select the Contact entity. 在您按一下或點選 [連接] 之後,實體便會新增至應用程式。After you click or tap Connect, the entity is added to the app.

新增連絡人實體

請注意,在此範例中我們從另一個實體新增資料,但您可以在應用程式中結合許多來源的資料。Note that in this example, we're adding data from another entity, but you can combine data from many sources in your apps.

查詢連絡人資訊Look up contact information

既然我們已可在應用程式中存取連絡人實體資料,現在正是加以運用的好時機。Now that we have access to the Contact entity data in our app, it's time to put it to use. 如簡介中所述,我們想要在案例更新時傳送電子郵件。As mentioned in the introduction, we want to send an email when a case is updated. 若要這麼做,我們將使用兩個公式和一個流程。We will use two formulas and a flow to accomplish this. 第一個公式將用於編輯畫面,特別是儲存按鈕的 OnSelect 屬性。The first formula is for the edit screen, specifically the OnSelect property of the save button.

應用程式編輯畫面

根據預設,當使用者編輯表單中的資料,此按鈕會使用公式 SubmitForm(EditForm1) 提交更新。By default, this button uses the formula SubmitForm(EditForm1) to submit the update when a user edits data in the form. 我們需要新增公式,使它先查詢開啟目前案例之人員的連絡資訊,然後將該資訊存放在本機應用程式︰We need to add to the formula so that it first looks up the contact information for the person who opened the current case, and then stores that information locally in the app:

UpdateContext({contact:LookUp(Contact, ContactId=BrowseGallery1.Selected.CurrentContact.ContactId)}); SubmitForm(EditForm1)

是,這是有點複雜,但從影片的 2:04 開始,James 會詳細解釋此公式。Yes, it's a little complex, but James does a great job of explaining this formula in more detail, starting at 2:04 in the video.

從應用程式觸發流程Trigger a flow from the app

既然我們已經知道每個案例的連絡人是誰,我們便可以傳送電子郵件給他們。Now that we know who the contact is for each case, we can send an email to them. 我們可以直接從應用程式傳送電子郵件,但此範例中我們將說明如何從應用程式觸發流程。We could send an email directly from the app, but for this example we'll show you how to trigger a flow from the app. 這就是流程,非常簡單︰根據應用程式中的動作傳送電子郵件。Here's the flow, which is as simple as it gets: send an email based on an action in an app. 我們不會在此詳細說明流程,但是您可以取得 Microsoft Flow 的完整引導式學習系列。We won't get into more detail on flows here, but there is a whole Guided Learning series for Microsoft Flow.

傳送電子郵件的流程

回到應用程式中,我們需要根據事件呼叫流程。Back in the app, we need to call the flow based on an event. 我們將使用編輯表單的 OnSuccess 屬性,以便編輯成功時會觸發流程。We'll use the OnSuccess property of the edit form, so the flow is triggered when the edit succeeds. 按一下或點選 [編輯表單],然後在功能區上按一下或點選 [動作] > [流程]。Click or tap the edit form, then on the ribbon click or tap Action > Flows. 選取您想要使用的流程。Select the flow you want to use.

傳送電子郵件的流程

流程現在與編輯表單的 OnSuccess 事件相關聯,而且我們可以參閱連絡人以取得電子郵件。The flow is now associated with the OnSuccess event of the edit form, and we can refer to the contact for the email. 下列公式會呼叫流程,而該流程具有已開啟案例之人員的電子郵件地址,以及電子郵件的主旨和本文。The following formula calls the flow with the email address of the person who opened the case, as well as a subject line and the body of the email.

CaseResolvedEmailConfirmation.Run(contact.EmailPrimary, "Your case has been updated", "Check it out")

這就是將資料來源新增至應用程式,然後觸發傳送電子郵件的流程。That's it for adding a data source to the app, and triggering a flow that sends an email. 如果您尚未看過本章節中的影片,我們鼓勵您這麼做。If you haven't watched the videos in this section already, we encourage you to do it. 這些影片具有大量我們在各主題中快速提過的詳細資料。They fill in lots of the details that we've moved through quickly in the topics.

結論Wrapping it all up

我們來到了此章節的結尾。This brings us to the end of this section. 我們希望您樂在其中,並獲益良多。We hope you've enjoyed it and learned a ton. 我們開始從實體產生基本的應用程式,並稍微探討應用程式,了解應用程式如何組合。We started out generating a basic app from an entity, and explored the app a little to understand how it's put together. 我們花了很多時間在自訂應用程式上,然後是新增資料來源,以及如何觸發流程。We spent a good deal of time on customizing the app, then added a data source and saw how to trigger a flow. 我們在本節中建立了特定的案例管理應用程式,但是您學到的技巧可以適用於許多類型的應用程式。We built out a specific case management app in this section, but the skills you learned could be applied to many types of apps. 如我們在這一節的開頭所述,如果您想要深入探討更複雜的案例管理應用程式,請務必查看 PowerApps Studio for Windows 中提供的範本。As we mentioned at the beginning of this section - if you want to dig into a more complex case management app, be sure to check out the template that's available in PowerApps Studio for Windows.

接下來,我們將移動到管理應用程式。Next up we'll move into managing apps. 管理章節會顯示共用的方式和版本應用程式,並介紹環境,也就是應用程式、資料和其他資源的容器。The management section shows you how to share and version apps, and introduces environments, which are containers for apps, data, and other resources.

恭喜!

您已完成 Microsoft PowerApps 引導式學習的 [從 Common Data Service 建立應用程式] 一節。You've completed the Creating an app from the Common Data Service section of Microsoft PowerApps Guided Learning.

您已學到如何...

下一個教學課程

管理應用程式Managing apps

參與者

  • Michael Blythe
  • olprod