cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Regular Visitor

Azure Service Bus: Pull vs Push, and Base64 woes...

I have a Service Bus Topic set up, and I'm sending messages to it from an Azure Function.  I am able to "Get" those messages using an AzureServiceBus data source.  However, I haven't quite achieved PowerApps/Service Bus nirvana.   I have two questions:

 

First, do I understand correctly that PowerApps doesn't currently have an "onMessage" functionality?  That is, must I always poll the Topic (or Queue) for a message; messages can not be pushed into PA?

 

Second, no matter what I do on the message creation side, I end up with a Base64-encoded string as the ContentData of my message.  If I write my own topic client, the message body is clearly JSON--or a String, if I send it that way.  No matter what I send, however, in my PowerApps message it's Base64 encoded.  I don't see a handy "Decode" function in the PowerApps list o' functions, so what am I supposed to do with the data as is?

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Advocate V
Advocate V

Re: Azure Service Bus: Pull vs Push, and Base64 woes...

Not sure if this is helpful but I ended up finding it easier to give up on JSON and just use the Properties table to pass the data to my Service Bus trigger.  It kind of already does the work for you but.. it is restricted to name / value pair and doesn't appear to support heirarchical structures.  Just a note that if  you use it you must structure it so each record is comprised of 'key' and 'value' columns that must be in lower case for the names.

View solution in original post

2 REPLIES 2
Highlighted
Community Support
Community Support

Re: Azure Service Bus: Pull vs Push, and Base64 woes...

Hi charleswstanton,

 

I referred to the documentation about Office 365 Outlook, there is a function about “On New Email”, it triggers a flow when a new email arrives.


So I check this trigger on the flow, I found that On new email is only available for Office 365 Outlook, Outlook.con, Gmail, but no one for Azure Service Bus.

1.png

 

About question2, currently PowerApps doesn’t have a Decode function. May I suggest you submit an idea at PowerApps ideas Forum about this function.
https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

 

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Advocate V
Advocate V

Re: Azure Service Bus: Pull vs Push, and Base64 woes...

Not sure if this is helpful but I ended up finding it easier to give up on JSON and just use the Properties table to pass the data to my Service Bus trigger.  It kind of already does the work for you but.. it is restricted to name / value pair and doesn't appear to support heirarchical structures.  Just a note that if  you use it you must structure it so each record is comprised of 'key' and 'value' columns that must be in lower case for the names.

View solution in original post

Helpful resources

Announcements
secondImage

New Return to Workplace

Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.

Check this Out

Helpful information

Featuring samples like Return to the Workplace and Emergency Response Applications

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Top Kudoed Authors
Users online (10,735)