Hi Rinse,
Apologies for the delay in response. You may already be using it, but you can do this using our List app's Append Item to List action. You can name the data pill there to avoid confusion. Let us know if you have further concerns!
This is not exactly what I mean I guess. I would like to rename the log or action labels, to make big app lists more easy to work with. Not sure how to solve this with append to list feature.
From the screenshot below, you can see that the name given to the list is reflected in the App data. The Field names will also be based on the field names you chose when creating the list. Is this what you meant?
No.. i would like to change the log message fieldname (label). Having ability to do this makes it easier to manage big recipes where log utility is used often. In my screenshot I have various log actions, but besides the step number I do not know what is logged.. So if we can change action name for log, it makes it easier to find the right logs.
Kind regards,
Rinse
I do understand that you want to use the Log Message action, however, you can substitute the Log Message action for the Append Item to List action instead to be able to name it. This is usable even if you only end up creating a list of one just to log the value in something you can customize. This is the best possible workaround while the engineering team has not yet put this particular enhancement on the road map. I hope this clarified it!
Aah ok, makes sense! Great!
Send us a ticket, we will try our best to assist you with your problem
Aremgi
Flow fields
Hi there,
In the screenshot below we are using the log function to get the right data into a single request and to avoid having complex formula’s as field values. So here we lookup data we check if it’s the right value and then we set those into a log. This work perfect and makes sense to work like this. However, having many logs it will create more invisible app data fields. Would it make sense to have an extra option to rename the log actions instead of only having the ability to comments. If we had the ability to change the log action ‘name’ then I would call this log ‘address 1’, then in the app data instead of having it named ‘Log message’ it would say something like ‘Address 1 (from log message)’. Otherwise we have to look back which step create a certain value.
Changing the action name for log would not need to be compulsory. Does it make sense?
If we have this ability it would be possible to create fields within a certain flow,
Let me know.
Kind regards,
Rinse