У нас вы можете посмотреть бесплатно Friday Functions Series | Part 2 PowerApps as a Flow Visual или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
This is part 2 of part 1 here: • Friday Functions | Sneak Peek of PowerApps... We learn more about the Flow that drives the process, the Flows that raise visibility to who's approving, as well as check out a few options for the information architecture. As a result, you'll know how to find out what's going on while Flow is waiting for the approvers to respond. I forgot to show you the items property for the visual gallery : It uses the 'approvers list' column to create single items and the other text is looked up. Items property of the visual gallery (the minus 1 removes the trailing semi-colon): Sort(Split(Left(GallerySubmissions1.Selected.ApproversList,Len(GallerySubmissions1.Selected.ApproversList)-1),";"),Ascending) Side Notes: -My reason for logging in SharePoint supports two of my goals: 1. Everyone can read the log list data (no permission issues for non-approvers and non-requesters), and 2. To expose the hidden responses which are accomplished during the 'wait for approval' action. -The approval CDS path works primarily from Approval to Approval Request to Approval Response, this is why the Approval Request trigger is used to grab the OwnerID (from the first request card) before the responses are submit. Then the flow triggered by responses adds approval records on SP as they are submit by the users. (If the Flow is cancelled, the app will persist with the gray state.) -The "approvers list" custom column is used to build the gallery with all approvers, even if they have not responded yet. Most important Entities and CDS fields involved here: -Approvals: msdyn_flow_approval_name (Approval ID) -Approval Requests: msdyn_flow_approvalrequest_approval (Approval ID) , msdyn_flow_approvalrequest_responseoptions (response options), and msdyn_flow_approvalrequestidx_owninguserid (approval owner) -Approval Responses: msdyn_flow_approvalresponse_approval (Approval ID), msdyn_flow_approvalresponseidx_owninguserid (approval owner), msdyn_flow_approvalresponse_response (approval response selected), msdyn_flow_approvalresponse_comments (approval comments provided) -Users: systemuserid (matches the owninguserid in the other entities) (ignore the id in the approvers json, focus on the owninguserid for approvers) Other Relevant Docs: Responses: https://docs.microsoft.com/flow/creat... Markdown: https://docs.microsoft.com/flow/appro...