Hello All,
I've been working on an App which works with several flows. Now I have gone through the trouble to put the app and all flows into a solution. While doing this (since you can't import manually triggered flows....) I've recreated all the necesary flows however on the first one I tested it immediately went wrong..
Here is a put together picture that should display everything:
Assuming since there is only 1 argument to be passed which is a date, the error can only concern the argument _Verzenddatum.
As we can clearly tell, Datepicker1.SelectedDate is passed as the argument which has always been the case for me and had always worked prior to now.
Edit: it would also be great if something were to be done about this horrible bug with flow names where renaming your flow does nothing.
In flows my flow is named 'PostMetaDataOpslaan' as shown here in connection details; however in powerapps formula's and in this tab it shows it as named 'PowerApp->Compose,Compose2,Condition,Updatefileproperties,Update.... etc (simply naming the actions).
I've tried recreating the flow as an entirely new flow, disconnect App from old Flow, connect App to new Flow, apply parameters correctly. :
same error. this is what is shown in the flow run history.
The Schema
{
"type": "object",
"properties": {
"Updatefileproperties_Id": {
"type": "integer",
"format": "int64",
"description": "Unique identifier of item to be updated",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_Aan": {
"type": "string",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_Afzender": {
"type": "string",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_Verzenddatum": {
"type": "string",
"format": "date",
"x-ms-powerflows-param-ispartial": false
},
"Condition_ObjectName": {
"type": "any",
"description": "Choose a value",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_Emailbehandelaar": {
"type": "string",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_Emailgeadresseerde": {
"type": "string",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_Kenmerk": {
"type": "string",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_Subject": {
"type": "string",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_Internkenmerk": {
"type": "string",
"x-ms-powerflows-param-ispartial": false
},
"Updatefileproperties_AfzendendeOrganisatie": {
"type": "string",
"x-ms-powerflows-param-ispartial": false
}
},
"required": [
"Updatefileproperties_Id",
"Updatefileproperties_Aan",
"Updatefileproperties_Afzender",
"Updatefileproperties_Verzenddatum",
"Condition_ObjectName",
"Updatefileproperties_Emailbehandelaar",
"Updatefileproperties_Emailgeadresseerde",
"Updatefileproperties_Kenmerk",
"Updatefileproperties_Subject",
"Updatefileproperties_Internkenmerk",
"Updatefileproperties_AfzendendeOrganisatie"
]
}
'Learn more' leads to a microsoft page:
https://support.microsoft.com/en-us/help/4540228/there-is-a-problem-with-the-flow-s-trigger
Hi @gjeh ,
Could you please share the detailed flow steps? Where does the argument _Verzenddatum apply?
From the error message, we can found that it seems to be a incompatible type issue.
Could you please share the Peek Code of PowerApps trigger to see if there is any incompatible type of arguments.
For example:
Hi @v-siky-msft thanks for your reply.
This is the peek code of my powerapps trigger :
{
"kind": "PowerApp",
"inputs": {
"schema": {
"type": "object",
"properties": {
"posttype_Value": {
"type": "string",
"description": "Enter initial value",
"isPartial": false
},
"Updatefileproperties_Id": {
"type": "integer",
"format": "int64",
"description": "Unique identifier of item to be updated",
"isPartial": false
},
"Updatefileproperties_Aan": {
"type": "string",
"isPartial": false
},
"Updatefileproperties_Afzender": {
"type": "string",
"isPartial": false
},
"Updatefileproperties_Verzenddatum": {
"type": "string",
"format": "date",
"isPartial": false
},
"Updatefileproperties_Emailbehandelaar": {
"type": "string",
"isPartial": false
},
"Updatefileproperties_Kenmerk": {
"type": "string",
"isPartial": false
},
"Updatefileproperties_Subject": {
"type": "string",
"isPartial": false
},
"Updatefileproperties_Internkenmerk": {
"type": "string",
"isPartial": false
},
"Updatefileproperties_AfzendendeOrganisatie": {
"type": "string",
"isPartial": false
},
"Updatefileproperties_BehandelaarID": {
"type": "string",
"isPartial": false
}
},
"required": [
"posttype_Value",
"Updatefileproperties_Id",
"Updatefileproperties_Aan",
"Updatefileproperties_Afzender",
"Updatefileproperties_Verzenddatum",
"Updatefileproperties_Emailbehandelaar",
"Updatefileproperties_Kenmerk",
"Updatefileproperties_Subject",
"Updatefileproperties_Internkenmerk",
"Updatefileproperties_AfzendendeOrganisatie",
"Updatefileproperties_BehandelaarID"
]
}
}
}
and this is how the verzenddatum is used in the flow (originally, i have also tried using compose and then putting the compose output in the update file properties block ; same result - the flow won't start)
Updatefileproperties_Verzenddatum was created by selecting 'ask in powerapps' in the orange circled field.
Keep in mind that I've already had contact with support about this issue twice where I am now at the point that this issue is being escalated to 2nd line support.
Was this ever resolved I am encountering the exact issue all of sudden?
Yes, I believe what I did was to create a new environment and instead of importing the flow to that environment i recreated it inside the environment from scratch.
Im pretty sure that's how I fixed it.
I've run into this issue too -- is there any other solution than trying to do everything in a new environment?
This is how i fixed it Text(datacardname.selectedDate,"[$-en-US]yyyy-mm-dd")..figured it out like two weeks ago 😕
Thank you so much, this was driving me nuts for a whole day, this solution works perfectly
User | Count |
---|---|
251 | |
250 | |
82 | |
45 | |
28 |
User | Count |
---|---|
348 | |
262 | |
127 | |
60 | |
58 |