Connect different software as a service providers with SharePoint through Azure Logic Apps. I was speaker at the local Azure Bootcamp (2016) in Sofia and after I decided to record short video on one of the demos I presented on the event. Of course it has relation to SharePoint and shows how we can connect it to different SaaS providers in minutes by using drag and drop first class designer directly in the Azure portal instead of building custom code.
Tough scenario is when you have to merge two branches of a solution with so many differences that one cannot simply be merged into the other. In this scenario I use SourceTree as GIT GUI client, KDiff3 linked to SourceTree as external merge tool to create DIFF patch from phase 2.0 set of commits and apply it to phase 3.0 branch. Bear in mind the two branches have many differences and I cannot just merge both in one merge action.
I tried to run flask app in Azure that generates matplotlib pie charts and save them as PNG. I use Windows, Visual Studio 2015 and Python Tools for Visual Studio. The publish to Azure Visual Studio option requires a virtualenv to be created, then flask app is deployed with it. Adding numpy from pip appeared to be challenge because pip was trying to first compile the package, but it failed every time due to missing Visual C++ packages, wrong VS100COMNTOOLS env var path or whatever.
Flask and SharePoint is Fun! I have created Python Flask scenario that shows how to set up authentication between a Python app (using the Flask microframework) and Office 365 SharePoint Online site. The goal of this sample is to show how a user can authenticate and interact with data from the Office 365 SharePoint site. So I was able lift up the Python Flask app in Azure and to connect to Office 365 SharePoint Online site with around 100 lines of code :). How cool is that!
I tried to run flask app in Azure that generates matplotlib pie charts and save them as PNG. However I encountered on two serious issues.
The good old times I used to do farm (full trust) solutions for SharePoint on-premise and there was very easy way to get list item versions data and work with it. Nowadays the Office365 / SharePoint Online offers limited support for this through the CSOM/JSOM framework, but it is not possible to get data for custom list item field.
This is a quick guide on how to set it up from the office 365 SharePoint admin center and test is with CSOM. In order to access the custom managed properties we have to add them under SharePoint -> SharePoint admin center -> Manage Search Schema.