วีดีโอ

Thank you :) I'll put this into my plan.

Yeah, the "DataMap" is only a custom name to action "Initialize variable" of "Variables" group of actions. This is basically definition of a json object which serves as a data-mapping structure.

Hi Jackson. Thanks for the comment! 😊 As for your question, the answer depends on your capabilities. If you are limited in using only Logic Apps (no-code), then you should shift to using Blob storage instead of File storage. In this ase you can use Event Grid subscribed to events in the Blob storage (blob create). Files are blobs in the Blob storage. BlobStorage -> Event Grid -> Logic App -> SharePoint If you are skilled in programming, you can develop an Azure Function with the File Share trigger. You can set it up to be triggered by a file creation event from a File storage. If you want to minimize programming than your Function should right away push the file, fetched from the File storage, to the HTTP trigger of your Logic App which will finalize the handling. The rest is the same as described in my video - you take the file and upload it to the SharePoint. FileStorage -> Azure Function -> Logic App -> SharePoint

thank you!

Thank you. Glad it helps. The solution depends on the specific issue you're facing. Let me know which part of the solution is the challenging part. Generally speaking: 1. Don't upload files from your local PC. You need the Logic App to access your files. I recommend uploading your files to a Storage Account in Azure (File Storage or Blob Storage). Then, give the Logic App access to the Storage Account. Enable a system-assigned identity in the Logic App and grant access to this identity in the Storage Account (using Role-Based Access Control). You can then use Logic App Storage Account actions to read files from the file/blob storage and transfer them to SharePoint. 2. I'm not sure I understand what you mean by dynamic properties. If you need to upload your files to SharePoint with specific file properties, you should define a Content-Type or columns in the SharePoint library where these files will be stored (this is metadata). By doing this, you can upload each file along with its properties. Each property will be displayed as a column in the library's list view. Any questions about any specific part of the solution?

Unfortunately, I don't have a scenario like that covered on my channel yet. However, you might find this video helpful: th-cam.com/video/SSfNhSnQo_g/w-d-xo.html. It focuses on using Azure AI, and I demonstrate it transferring files with use of Azure Blob Storage. And looks like your scenario is an interesting case for one of my future videos.

Hi! I appreciate your feedback and I'm glad you find my videos useful. I aim to make my videos a form of coaching by selecting topics and scenarios from my own experiences as a full-time IT consultant. All my videos are practical, discussing things I've used in my projects. I encourage you to leave your questions in the comments. Depending on the complexity of the problem, I'll either respond with a solution or create my next video to address it. Feel free to ask me anyway.

@@MaximKhoruzhiy Yep, we get extensive knowledge in your videos; I appretiate it.

Thank you. Your feedback inspires me to work further.

There is no standard way to edit workflow code in Power Automate, but I have found a copy-paste approach that serves as a useful workaround: Click on the action's ellipsis (three dots on the right side) and select "Copy to My Clipboard." Paste the content into your text editor and make the necessary changes. Click the "+" button and select "Add an action." Choose "My Clipboard" and press Ctrl-V. Your edited action will be added to the group. Select it and delete the old action. A word of advice: avoid using Power Automate for enterprise-scale automations and integrations. This technology is best suited for personal automations. I hope this helps. Please let me know if you have any further questions.

Thank you for your feedback. I'm glad that my videos help you. Unfortunately, I can't produce videos often as I'm full-time IT consultant, not a video blogger, but the videos I produce are based on the real life scenarios and experience, from developer's point of view. I hope this gives more value to the information I share.

The status code 502 means that there is a gateway between your azure function and the sharepoint site and communication with the SP fails. Your case is complicated by specific network topology which affects the communication. Is the SP site in the cloud (SharePoint Online)? Then your azure function is most probably in a VNet with specific routing rules and/or network devices and here is the cause of the problem. Is your SharePoint on premises? Then check the communication between the Azure Function and your local network. I would start with analysis of the network setup in your organisation's Azure tenant.

Thanks for the feedback! I'll start from the last one: I stored some extracted content data into SharePoint library along with the image file. It is very similar to storing in a database. Which DB did you mean? Query fields: fields are in the json object. Are you interested in querying json? Something else? Validation: yes, sounds reasonable. I'll put it into my plan. "Highlight something in the invoice": highlighting results of validation? Yea, sounds great. Do you have a similar use case? I'll put it into my plan. 👍

​@@MaximKhoruzhiy Hi Maxim, I Apologise for any confusion; I mentioned those points from the context of document evaluation (A good use case for many business processes and may help a lot of developers) One scenario is employees submitting multiple invoices for the Expense Claim process. 1) Invoice data is extracted (Optional - including some query fields in the invoice pre-built model to extract custom/additional Data) 2) Data is stored in a database to be compared (total amount mentioned by the employee and total calculated from the invoices (I don't know how easy this may be using SharePoint data) 3) highlight errors (mismatch) using bounding box (Polygon data) on the invoice. I know this may take a lot of effort and may not be part of your tutorial roadmap, and I totally understand that. Truly your tutorials are informative and acts as a good foundation for beginners

Thanks for the feedback. I'm working on it.

My pleasure :)

No, it is a standard action. For Each loop is an action in the "Control" action group which you can choose and set up according to your needs, however, Logic App designer will help you - in case you choose handling of a data element which is a member of a list/set/array, (for example you assign this element to a variable), the Logic App designer will automatically add the For Each loop so that this handling will be done for each element of the set in iterations. Let me know if still unclear.

Sorry, I'm afraid I don't understand the "...since you are moving back to a logic app http trigger", but if you asked about securing the Logic App generally, there are multiple options: First off, the http trigger is protected by default by a SAS key. You will find it in the HTTP trigger URL. In most cases it is enough for securing your Logic App. - If you want to apply more security measures, in the "Workflow settings" you can specify a range of IP addresses the Logic App will access requests from. - You can enable Azure AD Authorization Policy for you Logic App so that it will analyse the security token for the claims you specify in the policy (it is an alternative to the SAS key). - You have now option of using Logic Apps of Standard Plan type as opposed to Consumption plan. This one gives you a better networking isolation capabilities. - And you can protect your multi-tenant Logic App by ISE (Isolated Service Environment) which moves your LA out of multi-tenant environment. The last two solutions come with a higher price, so you should find a balance between security requirement and the selected measure. Hope this gave you some overview of the options to start with.

@@MaximKhoruzhiy thanks for your in depth answer. Really appreciated! 👍

My plesure@@MyNameIsDr Fell free to ask questions.

My pleasure. You may find something else helping on my channel and it is alive, there are more to come.

Thanks for the question. There are two approaches: the "release" controlled by the consumer (effectively - connector to the queue/topic) and "release" controlled by your own code running in the consumer. Both work equally well if your custom code comply the rules. Btw, "release" means - return the massage to the queue to be processed again. "Autom-complete" will always return the message into the queue/topic in case an unhandled error occurred. Using "peek-lock" you make your code more flexible about deciding when a message has to be released or completed. You may release and return the message into the queue even though there was no error in the consumer handler. Having said this, it depends, you decide. Auto-complete is simpler to use.

I'll provide the link to the code in GitHub in a while. I'll drop a message here.

The link to the GitHub repo is now available in the description to this video.

@@MaximKhoruzhiy thank you.. great video

Thank you :) My plan is to deliver more guidance content like this. Stay tuned.

Thank you. I hope you'll find more interesting content. I share my work experience and it's an ongoing process