TranslationExample: Using a "for-each" loop makes it impossible to know the final result as it would be blank if the node path being looped on doesn't exist.
- DynamicNodeAssistant.png (57.1 KiB) Viewed 6592 times
- DynamicNodeAssistant.png (57.1 KiB) Viewed 6592 times
Solution 1: Create a static blank record so that 1 instance always exists. It can even be set up in an "if" statement so that the blank record only exists if the node path being looped on doesn't. As long as a blank record will not cause issues, then this could be a viable solution.
- DynamicNodeExample1.png (98.67 KiB) Viewed 6592 times
- DynamicNodeExample1.png (98.67 KiB) Viewed 6592 times
Solution 2: If it's desired to not have a blank record that can mess with later logic, then a second disconnected service can be an alternative approach. In this case, the static blank record exists outside of the execution flow and thus can be referenced without a blank record existing at runtime.
If the original service is exposing it's output, then exposing the disconnected service as well will allow anyone calling the method to also be able to take advantage of the assistant.
The one downside of this approach is that the original service is also still in the assistant. This means that the assistant may or may not show the node structure depending on which version of the service was selected in it.
- DynamicNodeExample2a.png (25.22 KiB) Viewed 6592 times
- DynamicNodeExample2a.png (25.22 KiB) Viewed 6592 times
- DynamicNodeExample2b.png (76.28 KiB) Viewed 6592 times
- DynamicNodeExample2b.png (76.28 KiB) Viewed 6592 times