Questions on issues during Deployment #8
-
|
Hi, @peakers1976, I moved your question to the Q&A section I have had a couple of attempts at deploying the application with little success. It could be that I am missing something but I have followed the deployment guide step by step. The deployment of the script appears to work and I do not get any failure output.
The first problem I encountered is the secrets list/get permissions do not get applied for the service account, I need to manually add the account, the only accounts that get added are the app service principal name and the admin account I run the script.
The second problem is when I import the solution into PowerApps. the documentation states that I should be able to click next and define the variables, this does not happen, it only gives me the option to import.
I then have to manually go through and update the variables in the solution VAR - FunctionKey: value of the host function key additionally this variable
After I update the SharePoint site, I need to edit all of the Sharepoint list entries
Finally, none of the Cloud Flows are enabled by default "Not sure if this is by design" if i use the import-CallQueue flow to import auto attendants as per below steps: Automatically adding Auto Attendants Browse to https://make.powerapps.com/ first, I notice that the Get Secret has the incorrect secret name.
I need to update it with the correct result
The URI is incorrect for the POST method so I needed to update that. Finally, it fails with the following error
Any advice would be appreciated as it seems to be that some automation is not working as it should. Thank you, Originally posted by @peakers1976 in #5 (comment) |
Beta Was this translation helpful? Give feedback.
Replies: 14 comments 22 replies
-
|
@peakers1976 and @Josverl Thanks for your feedback and questions. It looks like that during the creation of the Azure Key vault the service account is not added for some reason. We will review the script and will update it to correct this issue. For now you can manually add the Azure Key vault service account and assign the get and list permissions. We saw some weird behavior indeed in some cases when importing the solution which requires that you update the variables manually. This is a remark we will add to our manual. The reason why the flows are disabled by default is because in your case the variables were not updated as part of the import process. If this happens the flows will be disabled to prevent errors occuring when running the flows. The secret name is a good catch we need to look into this as it should have an entry in the key vault normally. Hope this clarifies your questions. Johan |
Beta Was this translation helpful? Give feedback.
-
|
Hi Johan,
Thank you for your reply
Any idea about the failure of the flow with the importation of call queues
and auto attendants?
It does not appear the automatic functions work importing the existing CQs
and AAs.
…On Mon, 1 Aug 2022, 5:00 pm Johan Veldhuis, ***@***.***> wrote:
@peakers1976 <https://github.com/peakers1976> and @Josverl
<https://github.com/Josverl>
Thanks for your feedback and questions.
It looks like that during the creation of the Azure Key vault the service
account is not added for some reason. We will review the script and will
update it to correct this issue. For now you can manually add the Azure Key
vault service account and assign the get and list permissions.
We saw some weird behavior indeed in some cases when importing the
solution which requires that you update the variables manually. This is a
remark we will add to our manual. The reason why the flows are disabled by
default is because in your case the variables were not updated as part of
the import process. If this happens the flows will be disabled to prevent
errors occuring when running the flows.
The secret name is a good catch we need to look into this as it should
have an entry in the key vault normally.
Hope this clarifies your questions.
Johan
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7C6QVUU52NBOTZBIHBDVW6G2HANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@peakers1976 not without more details tbh, in our tests it worked fine so I do expect something going wrong. |
Beta Was this translation helpful? Give feedback.
-
|
I will investigate further and get back to you.
Thank you
…On Mon, 1 Aug 2022, 7:07 pm Johan Veldhuis, ***@***.***> wrote:
@peakers1976 <https://github.com/peakers1976> not without more details
tbh, in our tests it worked fine so I do expect something going wrong.
If you can share more details that would be great, for example do we
receive anything back when firing the Azure function or not
—
Reply to this email directly, view it on GitHub
<#8 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7C3IRI7CTSAZDYUTEA3VW6VW5ANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Johan,
I just wanted to check a couple of things with you.
Firstly I found where I need to change the variable in the deploy.ps1 for
the service account to receive the get/list permissions on the key vault.
The flows will not work, I suspect its because of the functions not working
In the deploy.ps1 code should this line be commented out?
[image: image.png]
If I do run that warmup.ps1 script it fails
[image: image.png]
I just have a feeling the reason the flow fails is that the function apps
are not set up correctly when the script deploys.
[image: image.png]
[image: image.png]
I was wondering if you could take some screenshots to identify what may be
missing on the function apps side
…On Mon, Aug 1, 2022 at 7:07 PM Johan Veldhuis ***@***.***> wrote:
@peakers1976 <https://github.com/peakers1976> not without more details
tbh, in our tests it worked fine so I do expect something going wrong.
If you can share more details that would be great, for example do we
receive anything back when firing the Azure function or not
—
Reply to this email directly, view it on GitHub
<#8 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7C3IRI7CTSAZDYUTEA3VW6VW5ANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@peakers1976 correct the deploy script was having an incorrect variable we added to our list to fix. Unfortunately, all screenshots are broken so it is hard to say what is wrong in your case |
Beta Was this translation helpful? Give feedback.
-
|
I have run the deployment at least 10 times and I am not sure everything in
the scripts applied correctly. The script runs without fault but none of
the functions work when triggered by the flows.
…On Tue, 2 Aug 2022, 6:31 pm Johan Veldhuis, ***@***.***> wrote:
@peakers1976 <https://github.com/peakers1976> correct the deploy script
was having an incorrect variable we added to our list to fix.
Unfortunately, all screenshots are broken so it is hard to say what is
wrong in your case
—
Reply to this email directly, view it on GitHub
<#8 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7C5YF5OLEUSW23VSB7TVXD2GZANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@peakers1976 I looked at the code again and it looks like the JSON file being used in prod did not contain name changes which clarifies why the Key vault names did not match the ones used in the different flows and the reason why the flow didn't return any output. Keep in mind that although the deployment might succeed it does not guarantee that the flows are working because the deployment script does not look at permissions etc. for the service account. I am waiting for 2 other team members to complete the review which will result in the deployment script as well as the JSON file to be updated which should fix some of the issues. What you can do in the meantime to troubleshoot the function which is not working is do the following:
|
Beta Was this translation helpful? Give feedback.
-
|
That's great thanks for the advice Johan.
Appreciate the quick response.
…On Tue, 2 Aug 2022, 8:52 pm Johan Veldhuis, ***@***.***> wrote:
@peakers1976 <https://github.com/peakers1976> I looked at the code again
and it looks like the JSON file being used in prod did not contain name
changes which clarifies why the Key vault names did not match the ones used
in the different flows and the reason why the flow didn't return any
output. Keep in mind that although the deployment might succeed it does not
guarantee that the flows are working because the deployment script does not
look at permissions etc. for the service account. I am waiting for 2 other
team members to complete the review which will result in the deployment
script as well as the JSON file to be updated which should fix some of the
issues.
What you can do in the meantime to troubleshoot the function which is not
working is do the following:
- got to the Azure function
- from the left menu select *authentication*
- temporarily switch of the authentication by pressing *edit*
- select *functions* from the left menu
- select the export-autoattendant or export-callqueue function
- in the left menu select *Code + test*
- wait for the function to load
- open up the log view on the bottom and make sure it is set to
Filesystem logs, you might get a warning but accept it for now
- on the top of the page you will see this bar:
[image: image]
<https://user-images.githubusercontent.com/13047574/182378157-0167d357-159d-49d0-8eb6-34eb691baee4.png>
- select the option **test/run** - in the new pane select **run** - wait
until the function completed - validate the output of the body and log
section
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7C57KSXJO3L3KFDDONTVXEKYTANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
thanks for reporting the issues you experienced so we could take the corrective actions |
Beta Was this translation helpful? Give feedback.
-
|
No problem, looking forward to using the app
…On Tue, 2 Aug 2022, 9:05 pm Johan Veldhuis, ***@***.***> wrote:
thanks for reporting the issues you experienced so we could take the
corrective actions
—
Reply to this email directly, view it on GitHub
<#8 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7C72VKXKZ3VT6MYNAMDVXEMJJANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hello, I am not sure if I should create a new discussion channel :), however I am facing strange error as well. I configured all as described and in my case I am facing issue directly on Azure function when I am importing call queues to share point list
Seems like PowerShell module load is broken. I have checked all variables, secrets, modules directly in function file store and all is ok. Have anybody experienced same issue please? Thank you |
Beta Was this translation helpful? Give feedback.
-
|
@stepan ok good catch so in this case if we would update it from this: If($cq.TimeoutActionTarget -ne $null)
{
If($(Test-IsGuid -StringGuid $cq.TimeoutActionTarget) -and $cq.TimeoutAction -ne "SharedVoicemail")
{
$TimeoutActionTarget = Get-CsOnlineuser $cq.TimeoutActionTarget
}
ElseIf($cq.TimeoutAction -eq "SharedVoicemail")
{
$authHeader = Get-AuthenticationToken
$TimeoutActionTarget = $(Get-GroupObjectInfo -Token $authHeader -ObjectId $cq.TimeoutActionTarget.Id).displayName
}
Else
{
$TimeoutActionTarget = $($cq.TimeoutActionTarget).split(":")[0]
}
}to this: If($cq.TimeoutActionTarget -ne $null)
{
If($(Test-IsGuid -StringGuid $cq.TimeoutActionTarget.Id) -and $cq.TimeoutAction -ne "SharedVoicemail")
{
$TimeoutActionTarget = Get-CsOnlineuser $cq.TimeoutActionTarget.Id
}
ElseIf($cq.TimeoutAction -eq "SharedVoicemail")
{
$authHeader = Get-AuthenticationToken
$TimeoutActionTarget = $(Get-GroupObjectInfo -Token $authHeader -ObjectId $cq.TimeoutActionTarget.Id).displayName
}
Else
{
$TimeoutActionTarget = $($cq.TimeoutActionTarget.Id).split(":")[1]
}
}So I modified the code based on your suggestion adding the .id property which fixed the issue if call forwarding is set to a single user and the phone last Else which was missing also the .Id. No let's look at the next issues with the call overflow because that one has the .id property. Regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hello Johan, I was able to go further with another call queue however flow is then failing for JSON not compatible schema
I fixed it but then it doesn't create an item in to the SharePoint probably due to different data inputs from source. I think if we want to reuse this app we need to validate whole data types. |
Beta Was this translation helpful? Give feedback.
-
|
@StepanFuchs looks like the JSON schema needs to be validated on the import-callqueue flow. This is probably caused by the fact by generating the JSON using a queue which had the overflow action. Based on this it added datatypes which might in cases no values are assigned causes errors. Think this one was overlooked as we did cleanup the auto attendant one. Below is how the JSON should look like: {
"type": "array",
"items": {
"type": "object",
"properties": {
"Name": {
"type": "string"
},
"AgentAlertTime": {},
"OverflowThreshold": {},
"OverflowAction": {},
"OverflowActionTarget": {},
"OverflowSharedTextToSpeechPrompt": {},
"OverflowSharedVoicemailAudioFilePromptFileName": {},
"TimeoutThreshold": {},
"TimeoutAction": { },
"TimeoutActionTarget": {},
"TimeoutSharedTextToSpeechPrompt": {},
"TimeoutSharedVoicemailAudioFilePromptFileName": {},
"UseDefaultWelcomeMusic": {},
"WelcomeMusicFileName": {},
"UseDefaultMusicOnHold": {},
"MusicOnHoldFileName": {}
},
"required": [
"Name"
]
}
}Regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hello Johan, I am reviving further scope of the project. I notice another complication, that power app filter is set to DisplayName, which is not valid for our purpose. I would need to change it to email instead
otherwise I am not able to join the data. Generally solution is well done and it would help us to replace missing BRAC over CQ and AA, which in skype is available :) I hope it help you to tune the project for other as well as I know, that MS officially plans similar kind of tool in the end of next year. However we would need to validate whole project and fix issue by issue. Thank you Stepan |
Beta Was this translation helpful? Give feedback.
-
|
Hi Stepan, First of all thanks for the help and testing you did. It has uncovered some issues which we didn't spot ourselves, so we are really happy with your help and support. I understand your requirements are a bit different and it would require a full review of the solution. Feel free to provide the new features or enhancement you would like to see and we can take them into consideration. The example you provided is for example a good candidate but would require some rework in our case |
Beta Was this translation helpful? Give feedback.
-
|
Hi Johan,
Just wondering if you had a chance to look at the logs from the
export-callqueue function and shed some light on the problem?
…On Wed, 3 Aug 2022, 2:52 pm Nathan Peacock, ***@***.***> wrote:
Hi Johan,
I followed the steps to disable the authentication and output the logs to
the filesystem
Please see the attached log, it does not complete
On Tue, Aug 2, 2022 at 8:52 PM Johan Veldhuis ***@***.***>
wrote:
> @peakers1976 <https://github.com/peakers1976> I looked at the code again
> and it looks like the JSON file being used in prod did not contain name
> changes which clarifies why the Key vault names did not match the ones used
> in the different flows and the reason why the flow didn't return any
> output. Keep in mind that although the deployment might succeed it does not
> guarantee that the flows are working because the deployment script does not
> look at permissions etc. for the service account. I am waiting for 2 other
> team members to complete the review which will result in the deployment
> script as well as the JSON file to be updated which should fix some of the
> issues.
>
> What you can do in the meantime to troubleshoot the function which is not
> working is do the following:
>
> - got to the Azure function
> - from the left menu select *authentication*
> - temporarily switch of the authentication by pressing *edit*
> - select *functions* from the left menu
> - select the export-autoattendant or export-callqueue function
> - in the left menu select *Code + test*
> - wait for the function to load
> - open up the log view on the bottom and make sure it is set to
> Filesystem logs, you might get a warning but accept it for now
> - on the top of the page you will see this bar:
>
> [image: image]
> <https://user-images.githubusercontent.com/13047574/182378157-0167d357-159d-49d0-8eb6-34eb691baee4.png>
> - select the option **test/run** - in the new pane select **run** - wait
> until the function completed - validate the output of the body and log
> section
>
> —
> Reply to this email directly, view it on GitHub
> <#8 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEMZ7C57KSXJO3L3KFDDONTVXEKYTANCNFSM54RWDAEQ>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
|
@peakers1976 maybe I missed it but I don't see any logs from you but it is likely the same issue as Stepan is seeing |
Beta Was this translation helpful? Give feedback.
-
|
Possibly, I attached a log file to the email maybe it didn't go through.
Any chance you work for Microsoft? I noticed someone with the same name as
yours in the address book on teams.
…On Fri, 5 Aug 2022, 8:55 pm Johan Veldhuis, ***@***.***> wrote:
@peakers1976 <https://github.com/peakers1976> maybe I missed it but I
don't see any logs from you but it is likely the same issue as Stepan is
seeing
—
Reply to this email directly, view it on GitHub
<#8 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7C5KVNG7T3W4RMZHRT3VXUFNJANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
yes ;-) so feel free to send it directly |
Beta Was this translation helpful? Give feedback.
-
|
All I am going to mark this discussion as closed. We released a new version of the Azure Function App which should fix most issues which are reported, a small description about the changes can be found: here |
Beta Was this translation helpful? Give feedback.
-
|
Hi Johan,
I followed the steps to disable the authentication and output the logs to
the filesystem
Please see the attached log, it does not complete
…On Tue, Aug 2, 2022 at 8:52 PM Johan Veldhuis ***@***.***> wrote:
@peakers1976 <https://github.com/peakers1976> I looked at the code again
and it looks like the JSON file being used in prod did not contain name
changes which clarifies why the Key vault names did not match the ones used
in the different flows and the reason why the flow didn't return any
output. Keep in mind that although the deployment might succeed it does not
guarantee that the flows are working because the deployment script does not
look at permissions etc. for the service account. I am waiting for 2 other
team members to complete the review which will result in the deployment
script as well as the JSON file to be updated which should fix some of the
issues.
What you can do in the meantime to troubleshoot the function which is not
working is do the following:
- got to the Azure function
- from the left menu select *authentication*
- temporarily switch of the authentication by pressing *edit*
- select *functions* from the left menu
- select the export-autoattendant or export-callqueue function
- in the left menu select *Code + test*
- wait for the function to load
- open up the log view on the bottom and make sure it is set to
Filesystem logs, you might get a warning but accept it for now
- on the top of the page you will see this bar:
[image: image]
<https://user-images.githubusercontent.com/13047574/182378157-0167d357-159d-49d0-8eb6-34eb691baee4.png>
- select the option **test/run** - in the new pane select **run** - wait
until the function completed - validate the output of the body and log
section
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7C57KSXJO3L3KFDDONTVXEKYTANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Nice 😊
I will try not to annoy you to much.
If you have some spare time one day next week maybe we can touch base to
screen share and I can show you the issue.
Thanks Johan
…On Fri, 5 Aug 2022, 9:12 pm Johan Veldhuis, ***@***.***> wrote:
yes ;-) so feel free to send it directly
—
Reply to this email directly, view it on GitHub
<#8 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMZ7CY76HVDERELRMBV4HTVXUHL3ANCNFSM54RWDAEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
All I am going to mark this discussion as closed. We released a new version of the Azure Function App which should fix most issues which are reported, a small description about the changes can be found: here