This one is to save you a lot of time. I am unsure, how many people are still to upgrade but sharing anyway.
Issue: When you upgrade from web client to UCI, some columns in the views will show as blank.
Reason: I couldn’t find any reason and then Microsoft came to rescue. This might occur because the missing data column is not in the FetchXML of the view. UCI depends on the view metadata to retrieve data from server. In web client this was different.
Solution: Remove column and add it back, save and publish. And the data will start appearing again. Make sure to do this in dev/test/sandbox environment first and then move the solution to production.
In this video we are talking about how to make your bot smart enough so the bot is aware of Portal User’s name. And skip the question of asking name, email etc. completely because the user is already logged in to the portal.
In this blog we are talking about how to show/hide a bot of users preferred language on Power Apps Portals.
Power Apps Portals provides a field on user profile called ‘Preferred Language’. That’s the only way you know what is your users preferred language. Instead of using the default ‘Preferred Language’, I created a text field on user profile also called ‘Preferred Language’ (different schema name though)
Now in the video I am using Preferred Language as a filter to show either english or spanish bot based on what is the value in preferred language field of user’s profile. if the field is blank, we can show probably english or any other language which is mostly spoken in your region.
In this video, I am talking about three new features that were released between April-May 2020.
Bot Variables/Global Variables
Support for additional languages
Adding your chatbot to a Power Apps solution
Bot Variables– The new variables allows you to select one of the two options; local or bot. if use select local then you can use the variable only in that specific topic while if you select bot then you can use the variable across topics in your bot. Moreover, you can now use variables in external sources like websites.
Support for Additional Language– You can now make your bot in multiple languages, providing you a global reach. Along with English you now 15 more languages in preview and should be available generally soon. There are three more languages which are in experimental state, namely Hindi, Korean and Polish.
Working in a solution– You can now add your chatbots to a solution in Power Apps makers portal. All the components are added within a solution. The solution can then be exported or imported depending on your needs.
In this blog we are going to talk about emojis in Power Virtual Agents. We will also touch upon GIFs and images but mostly Emojis. First of all, if you were not aware that you can use emojis in PVA, I am telling you can and that too #thecodeway. Watch the video to see it working.
If your question is why am I talking about something which is available Out of the box and is a no brainer; my answer would be:
I have not seen emojis being used yet in PVAs (Silly side of me)
Main reason: User Experience (UX) is the reason I am writing this blog.
Add some emotional intelligence to your PVA
It saves your canvas in your PVA.
Emojis are used by more than 3 billion people (and growing) which makes it the most spoken language in the world. One picture is worth ten thousand words.
For good UX your bot needs to react to different types of messages not just text.Knowing that PVA is still new in the market and is being continuously updated, there might be some emojis which you can’t use (No, I haven’t tested all 20,000 of them 😀)
Using emojis can be a great way of defining your chatbots personality and it can make the conversation casual increasing the engagement rate.
In terms of using a GIF or Image as your PVAs response, use the following and it will be shown to the user. Yes, I am also waiting for the adaptive cards #thenocodeway.
Let’s watch the video, if this interests you. Following is covered in the video:
This is the last episode of Agent, Power Virtual Agent series. Playlist here
This episode of Power Virtual Agents (PVA) is about how to identify and verify your customers in PVA. In Episode 5 we looked at authenticating internal users but what if we want to verify customers before providing them in any information.
We are going to achieve this with the help of a Power Automate Flow and PVA variables.
Refresh body template -refresh_token={RefreshToken}&redirect_uri={RedirectUrl}&grant_type=refresh_token&client_id={ClientId}&client_secret={ClientSecret}
Scope list delimiter “,”
Token body template -code={Code}&grant_type=authorization_code&redirect_uri={RedirectUrl}&client_id={ClientId}&client_secret={ClientSecret}
