MANUALLY SET the URl to the Microsoft SharePoint site:ĭEFINE 2 new Microsoft Flow “parameters” ie “dynamic content” that will actually come from PowerApps when it calls this Flow (like it would any other method). Microsoft Flow Designer automatically launches in a new browser tab (handy!):ĪDD a New Step > Add an Action > SharePoint > Create File. SELECT the btnUpload button, then SELECT Action > Flow > Create a New Flow to begin creating a new Flow (follow numbers in screenshot): This has become a best practice for me that I heartily recommend!) (note: if you see an unusual amount of “SAVE-AS” being done, it’s because I’ve learned several hard lessons losing vast amounts of coding while developing PowerApps. TEST & DEBUG until this functionality is working: TEST this “binding” functionality so far, and troubleshoot until you get it working:ĪDD another “Set()” function to the btnCapture’s OnSelect event handling this will set a new internal variable “_txtImageFilename” with a nicely-formatted filename based on the current time (handy): WIRE-UP the Image Control to get its “Default” value from this internal variable “CapturedImage” (this is how PowerApps work) WIRE-UP the Camera Control to “Set” (populate) an internal variable “_CapturedImage” INSERT the following key elements onto the main screen: Time to look at the “recipe”” for this PowerApps Cookbook entry: RECIPE:ĬREATE a new SharePoint Picture Library in your o365 environment in my demo, I’ll name this CAMERA_PICTURES use only the default fields (you can customize this later)ĬREATE a new PowerApps apps using the “blank” app template and “phone” layout (we’re keeping this recipe to its bare essentials) Put another way, you’re triggering a popular FileCreate Microsoft Flow from a PowerApps button click, but transforming the “image” data coming out of PowerApps before it actually populates the “File_Content” field in the FileCreate Flow. UPLOADS this binary content into a Microsoft SharePoint Picture Library using the second built-in “File Create” Action which accepts 4 inputs and uploads a file.TRANSFORMS the “URI” encoding into BINARY (read “image”) using the first built-in “Compose” Action which executes a built-in Data API function “ dataUriToBinary()“.A variable _imgCapturedImagewhich is a Base64-Encoded block of text which represents the “raw” image captured by the smartphone’s camera.A variable strImageFileName which will be the filename for the JPG image and.RECEIVES 2 parameters from the PowerApps app:.CALLS a custom Microsoft Flow (comprised of only 2 built-in Actions) which:.CAPTURES image content (as Base64Encoded text). ![]() We have uncovered a PowerApps and Microsoft Flow solution which: However, recently myself and others have explored the ever-increasing features of PowerApps and Microsoft Flow, and now a quite-acceptable (even clever) solution has emerged! SOLUTION: PowerApps + Microsoft Flow
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |