|Flow BLOG||Whats going on with Flow|
|Flow PRODUCT UPDATES|
|POWER SUMMIT PHOENIX|
|Flow User Group|
|Limits and configuration in Microsoft Flow||Max 5000 items, Premium 100.000|
|FLOW Ideas||Ideas submitted to the MS Flow Development team.|
|SQL Server – Known Issues and Limitations||SQL Server on-premises : Trigger does not work on create Item (insert row)|
|Calling Microsoft Flow from your application||Uses Postman to trigger flow. Also demo of JSON schema etc.|
|What about URL security?||A: Azure securely generates logic app callback URLs using a Shared Access Signature (SAS). This signature passes through as a query parameter and must be validated before your logic app can fire. Azure generates the signature using a unique combination of a secret key per logic app, the trigger name, and the operation that’s performed. So unless someone has access to the secret logic app key, they cannot generate a valid signature.|
|JSON Schema Validator||Validate schema using JSON data|
|Do bulk insert/update in Microsoft Flow with two simple elegant filter-arrays|
|callback http post||webhook|
- Microsoft Flow
- MS Flow/SharePoint Performance
- MS Flow – Nice to know
- MS Flow – Update List / Library Items
- MS Flow – Missing features
- MS Flow – Useful Links
- MS Flow and Excel
Need more help with this?
DON'T HESITATE TO CONTACT US HERE ..
Thanks for your feedback.