I am getting this error message:
InvalidTemplate. Unable to process template language expressions for action 'Condition' at line '1' and column '3364': 'The template language expression 'body('Get_item')['EmployeeLoginID']' cannot be evaluated because property 'EmployeeLoginID' doesn't exist, available properties are 'value'. Please see https://aka.ms/logicexpressions for usage details.'.
this has happened after I added several conditions to my "Apply to each" .
My current flow:
The two conditions here are "Employee_PrimaryLoginID" and "EmployeeID"
This is particularly strange as I didnt have this error before, then after appending so more conditions beneath this condition I am getting this error.
Any help would be appreciated.
This problem happens sometimes when you introduce new connectors to a flow after you have initially saved the flow without using that connector.
You can choose the following solutions：
1.Recreating new flow from scratch solve the issue.
2.Go to the Power Automate, export your flow. Then, Import your flow ( as a new flow).
Reference:
Unable to process template language expressions in Custom Connector
The issue sometimes occurres when the field value is null on CRM. Because of that the Dataverse connector didn't return the field name in the output so when trying to get the value of the field it returned the above error.
An alternative solution for this issue is to check if the field exists before getting its value, like this :
if (contains(body('Get_item'),'EmployeeLoginID') , body('Get_item')['EmployeeLoginID'],'')
Related
I have a flow, that gets triggered when a file is created in the Documents. The flow will add a column to the document library. The problem is that the modified by field in the Document library always contains the value as my name, instead of showing the user who triggered the flow.
I have already followed this article and seems like that is not working on my end.
After doing those changes, my flow runs fine without any error and giving an output as proceeding.
{
"d": {
"ValidateUpdateListItem": {
"__metadata": {
"type": "Collection(SP.ListItemFormUpdateValue)"
},
"results": [
{
"ErrorMessage": null,
"FieldName": "Editor",
"FieldValue": "[{\"Key\":\"i:0#.f|membership|nk#fdgfsgfs.de\"}]",
"HasException": false,
"ItemId": 1
}
]
}
}
}
But there are no changes in the Document library, it still shows my name in the modified by column as I created the Flow. Even if this worked, I have another question that how can I dynamically find out and add who is triggering the Fow instead of giving a static editor claim in the first Compose step in the above image?
Anyone else faced this issue? Any help is really appreciated.
I do not think it is possible at the moment to dynamically find the current logged in user. you can check out this post
https://powerusers.microsoft.com/t5/Building-Flows/Flow-to-SharePoint-list-item-change-quot-Created-By-quot/td-p/93668
I could solve this issue by using the REST API in the flow itself. This is what I did,
Get the user who called the flow
Update the Modify field by using the REST API in the flow itself
This blog post will help.
Wondering if you could help with this problem please. I am ingesting data from an API using Azure logic App. I have managed to set up everything else but struggling with pagination in Until condition.Logic App continues to ingest/consume data and creates blank json files with data[]. I have added the screenshots (with and without data in the page). When data is completed, empty or blank page looks like data[].
Any idea what could be my condition in "Until" ?
enter image description here
In your question I can't see the "Until" condition but just a "If" condition, but I think you just want to know how to check if the "data" field is empty and then do different actions (If I misunderstand your requirements, please provide more details and I will try to help you on it).
Please refer to the steps below:
1. We need to use a "Parse JSON" action to parse your json data, when click "Use sample payload to generate schema", you can put the json data which "data" field is not empty into it. And then it will generate the schema automatically.
2. Then we can use "length()" method in the "If" condition.
The whole expression of "length()" method above is:
Below provide the code for you to copy.
length(body('Parse_JSON')?['data'])
Hope it helps~
I have developed Netsuite Rest API using 2.0 code and in GET method I am returning list of entities. This works ok if the list is not including a field which has custom segment tagged to it.
If I include this field i get below error in reponse
An nlobjSearchColumn contains an invalid column, or is not in proper syntax: custentity..
I have given custom segment permission to the role. Does anyone have similar experience? What is the solution for this?
You should add an example of the code in question. Specifically where the error is being returned from.
I have also seen some people say to change the visibility of the field(s) on the record, retest, then reset the display back to normal.
Also, just to clarify, you are not using nlobjectSearchColumn in 2.0, correct? That is a 1.0 function, not a 2.0 function. The 2.0 version is s.createColumn.
I'm able to upload classification to Maximo except CLASSSTRUCTUREID column, the process of MxLoader finish without any errors but the class structure field gets an Autokey value.
I tried to remove the Restricted option from the integration object structure (enforced to check Override) but on third row I got this error:
Internal Server Error
Error 500: nested exception is: psdi.util.MXRequiredFieldException: BMXAA4195E - The Class Structure field requires a value."
The first two lines updated successfully on Maximo but, the other lines got the classification id in Classification Path and empty the parent classification (screenshot attached)
Any suggestion
Thanks
Maximo: 7.5.0.3
MxLoader: 4.7.2
in Maximo, after removing the restriction option from the integration object structure you must use option "Generate Schema/View XML" from action menu, for both Create and Update Operation.
it works with me after doing this.
I have some javascript code attached to the accounts entity. This code sets the requirement level of the primary contact attribute based on the value of a custom option set field showing various account types. This was developed on one server, where it worked, and so the solution was imported into another organisation where it now doesnt work.
It seems to be only on this field as i have changed the code to look at another field and that works fine. The error it gives is that the "Object doesn't support this property or method". Also what is strange is that the field doesn't appear in the list under the entity within the solution despite it being a system field.
The code i'm using is:
Xrm.Page.getAttribute("primarycontactid").setRequiredLevel("required");
Can anyone help me figure out what it's doing?
Thanks
EDIT: Found that the code is actually making the field required despite the error, but it's not displaying the * next to it. Also if I make the field required in it's settings then it does the same thing