Working with Sharepoint On-Prem data with PowerApps

To work with Sharepoint On-premise data you will need On-Premise data gateway. It acts as a bridge to your data to work with it on Power BI, Microsoft Flow, Logic Apps, and PowerApps services. Sounds fantastic, eh? Not so much.

 

Exploring this option I found caveats on using On-Prem Sharepoint with PowerApps.

 

Many columns are not available in Sharepoint On-Prem but available in Sharepoint Online

  • The list attachment – The list attachment column is not available in On Prem but available in SP Online. Sure you can Add/update/delete list items from your PowerApps form to Sharepoint On prem however you will not be able to add an attachment.

 

  • The link for an item in a document Library – Let’s say you are working with a document library and you want to view/download that item using the direct link to the document. It’s not available in On-Prem but available in SP Online.
  • onprem link
    Limited available OOB columns in Sharepoint On-Prem
    powerapps direct link
    Sharepoint online shows more available columns you can use

    Clearly the On-Prem(2013 and 2016) is behind the Sharepoint online and would present problems when working with PowerApps and/or Flow. Hopefully on the upcoming 2019 version we’ll see them addressed. 🙂

Simple Approval workflow using Nintex for Office 365

Requirements: Create a one level of approval for requesting office supplies. Send an Email to the user when his request has been sent for approval and send an email when the request has been rejected or approved.

In this scenario we will be creating a custom list with the following fields:

  • Item requested (text)
  • Quantity(text)
  • Manager(People)
  • Supplies type(choice)
  • Details(text)

 

custom list

Now we start creating the workflow. Click Nintex workflow. create nintex workflow.png

From the Workflow Designer click workflow settings, assign name to the workflow and choose “start automatically when item is created”.

workflow settings

Now we proceed creating the steps of our workflow approval.

Step 1: The first workflow action that we will add is “Send an email”. You can add this by dragging from left pane to the node after start process. This will notify the user once the request has been sent for approval.

Step 2: Let’s configure the email details by double clicking the “Send an email” action.

Step 3: Now let’s add a “Set workflow status” action to update status of our workflow. We will set the status to “Pending Approval”.

Step 4: Start assigning a task to the current item’s approver/manager field by adding a “Start a task process” action. Add the manager field as participant. Allow lazy approval.

task process participant

Step 5: Add “Set workflow variable” action on each branch and set our variable approvalStatus to “approved” and “rejected” accordingly.

build string

Step 6: Add “Build string” action to compose our email message using the variable “approvalStatus” and name the output as “emailMessage” variable.

 

Step 7: Now we could set the “status of the workflow” and “Send an Email” using our variables.

Step 8: Save and Publish workflow.

Here is an overview of the finished workflow:

Finished workflow

Creating new item and testing workflow:

 

Thats it! Its really pretty straight forward.

 

 

 

 

 

Power query issue in office 365 when site is not in english

d43660555a8e000f99d200f449f6035b

I was really excited to get my hands on Power BI on Office 365 for the first time but then a few moments later I got into a black hole.

Power Query is not returning any data from a sharepoint list. After hours of finding my way and looking around the web. I finally  came across the answer to this issue and I have found out that this is a present bug on non-English site.

Issue Description: Power query fails to get data from sharepoint List when site is not in English

References:

Power Query error when connecting to Office 365 SharePoint site Use English as your #0365 (sub) site’s default language or else…(use oData)

power query

 

**************

Update:

Turns out Odata Feed as an alternative is the better way to go.. 🙂