Fix bug for running single flow nodes with nested dict inputs

[pjanowski]

Description

Inputs like ${parent_node.output.result.inner_key} will fail because of how the inputs are currently written to the jsonl inputs file. Eg.

{"parent_node.output.result.inner_key":{"result":{"inner_key1":"foo","inner_key2":"bar"},"metrics":{"mertric_1":1.2}}

This is different behavior than when running entire flow where the input is always keyed on "parent_node.output.result" rather than "parent_node.output.result.inner_key".

All Promptflow Contribution checklist:

• The pull request does not introduce [breaking changes].
• [] CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.
• I confirm that all new dependencies are compatible with the MIT license.
• Create an issue and link to the pull request to get dedicated review from promptflow team. Learn more: suggested workflow.

Fixes #3882

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• [ x There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[github-actions]

SDK CLI Global Config Test Result patch-1

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 4f0dcbb.

[github-actions]

Executor Unit Test Result patch-1

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 4f0dcbb.

[github-actions]

Executor E2E Test Result patch-1

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 4f0dcbb.

[github-actions]

Hi, thank you for your interest in helping to improve the prompt flow experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment.

[pjanowski]

@MilesHolland @ninghu @luigiw Can one of you review please? Has been submitted for review since 12/7/24. Thanks!

[w-javed]

Can you add unit test to support this change.

[github-actions]

Hi, thank you for your interest in helping to improve the prompt flow experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment.

[pjanowski]

still active

[github-actions]

Hi, thank you for your interest in helping to improve the prompt flow experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment.

[github-actions]

Hi, thank you for your contribution. Since there has not been recent engagement, we are going to close this out. Feel free to reopen if you'd like to continue working on these changes. Please be sure to remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.