fix(target_actor): use 'name' instead of 'completename' for user and supplier actor types #3619
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…supplier actor types
btry
approved these changes
Oct 23, 2025
Rom1-B
approved these changes
Oct 23, 2025
stonebuzz
approved these changes
Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes description
When exporting a form, if a target is predefined with an actor of type “Specific Person,” the actor_value in the JSON is set to null.
This problem arises because the plugin attempts to retrieve the completename field for actors of type user or provider, even though this field does not exist in these cases.
The name of the user (or supplier) is actually stored in the name field.
Actor:
JSON before fix:
JSON after fix:
Checklist
Please check if your PR fulfills the following specifications:
References
Closes !39806