So the other day I was playing around with some field manipulation in PowerApps and thought about a use case I saw often with respect to updating fields when code from a button or some other action occurs. Say for instance you wanted to update a hidden field with some information when a user clicked a button or completed some task on the form. Maybe it isn’t a hidden field, but whatever the case may be, you need to be able to update that field. I was surprised to note that it isn’t very intuitive in PowerApps, nor could I find much out there in the forums. I did find some information around doing it with a Text Input field, but nothing specific to a data card.
When building your data views in PowerApps, the items can look a bit blended together. You can add separators, but things may still not look quite as nice. For example, a simple view of the data (in this case the contents of a list) may look like this:
This looks ok, but I would prefer to have each item be a bit more distinct.
Are you looking at getting your employees more engaged with the tools you are using? Are you looking to increase your efficiencies at your workplace in order to meet your business goals? Then I suggest you take part in a free webinar hosted by Microsoft on March 20th. In the webinar you will hear from other companies discuss how they engaged their workforce. The webinar will provide insight into trends, challenges, and opportunities that influence the employee experience. The webinar will help you understand how technology can drive and support change in your workforce by connecting everyone together at all levels within your company.
Kathleen Hogan, Chief People Officer at Microsoft, will also discuss how connecting their employees created a work culture transformation. You will get to hear Microsoft’s external colleagues discuss stories, best practices, and business outcomes from employee engagement and communications initiatives.
Thanks for reading!!
While planning out a new series I want to do around PowerApps and Flow I realized one of the things I needed to do was get the value of a lookup field into a text field. Now we all know that using a calculated field for this isn’t going to work since they can’t see lookup fields. Yes I could use a choice field instead, but in this case I wanted a lookup field so that the users could easily update the choices from the lookup list. There are a number of examples of doing this with a SharePoint Designer Workflow. So I got thinking, but about Flow? I found a number of examples of users asking for ways to do this or having problems doing it, but nothing really concrete. So I decided to write something up quick as it really is very easy to do with flow.
These days it is really easy to create lists and libraries to store data and documents. It is also very easy to build metadata to support the information you are trying to store. However, as I have stated before it is also very easy to set things up incorrectly. This next post in my Power User Best Practices is going to cover what you should and shouldn’t do with a SharePoint List and Library.