Web components have been a topic of conversation for some time, but I had never had a reason to really take time to explore building an application using them. There are many different reasons, with the biggest one being that many of the projects I have been working on utilize some of the big component libraries like Kendo or DevExpress. Continue reading “First Adventure into Web Components”
Microsoft Flow is a very powerful product and it is getting better all the time. However, I wanted to build a flow that would automatically create a date in the future when creating tasks on my Trello board. There isn’t anything built into Microsoft Flow Actions that does this (at the time of this blog post), but it can be done using Microsoft’s Workflow Definition Language.
Since I am unable to post comments directly to this page because Disqus is refusing to send a verification email, I am posting the question here and hope someone can provide answers.
I understand building relationships, but I need to be able to do more than use a relationship in a lookup. I need to be able to display related records from an entity based on a currently selected entity in a parent table.
For example, say I am building a work order tracking system for techs and customers. I have a work order entity and a work order history entity I would like to use. The work order tracks the original request from the customer while the history tracks the individual touch points a tech has made with the customer. I have a screen that displays the details of the work order. I want to be able to display the full history of the work order (and add more records) by going from the currently selected entity. This scenario is almost entirely missing, and in my opinion a much more common use of relationships in entities.
Are there plans to support related data in a much more comprehensive manner? If not, this could be a very limiting factor with using both the common data model and PowerApps since a lot of data structures make use of relationships to expose related data.
In this post, I hope to give you some ideas of how easy it is to use Microsoft Flow as I walk through how I created a really simple flow. The flow looks at my Twitter timeline and captures Tweets that contain a specific keyword. When it finds tweets that match, a card is created on my Trello board so I can review it later. This scenario could easily be expanded for an organization that wants to monitor a product launch or needs to field support requests from customers or clients and have them tracked by a team in Trello.
Before we begin, let me introduce you to Microsoft Flow. It is a new service currently in preview that allows you to “Create automated workflows between your favorite apps and services to get notifications, synchronize files, collect data, and more.” If you have used web sites like IFTTT or Zapier, you may be familiar with the general idea of Microsoft Flow. These tools allow you to build workflows between various internet based applications.
For example, I have an IFTTT recipe that automatically puts my cell phone on silent any time I reach my office building and another IFTTT recipe that notifies me if my Nest thermostat detects my house has reached 80 degrees (uh oh, time to call the A/C repairman). The focus of these tools is to make it easy for a user to automate a small task.
This is just a quick little snippet you can add to a SharePoint 2013/O365 SharePoint Site to automatically turn on Full Screen Mode when you load a page within the site and how to turn it back off when you exit that page.
Recently, one of the summer interns at my company was tasked with creating an expense report solution utilizing O365, Nintex Forms for O365 and Nintex Workflow for O365. As the expense report moves through the approval phases, permissions need to be altered so the original report that has been submitted cannot be changed by the author. This allows the approver to review the expense report without alterations occurring after approval.