You can create a microflow to open the registration form, and in this microflow you can change whatever you want: including changing a Name string to contain the name of the current user. Retrieve the account using the xpath [id = '[%CurrentUser%]' , and change your registration.name attribute to $Account/Name. Hope this helps!
You can achieve this using a BeforeCreation-microflow on the Registration-Entity.
Works now, thank you both!
Why do you want to store the name in the Registration?
I would opt for a reference to the user and show the name over association.
This also used in the Rapid Developer learning path: http://learn.mendix.com/link/path/10
Using an association IS re(use) of data instead of duplicating it what you try to achieve.
And also this can be set automatically, just like Wieke described. But instead of copy/pasting the name in a attribute, you can set the association to the current logged-in user.
Additionally, split your account data (ability to login) from process data (who you are in a process)
See this topic: https://forum.mendix.com/link/questions/88682
Got it. Thanks for your valuable input. After making the suggested changes I keep on getting the following message:
Do you have any idea how to fix this?
For the New button which Invokes a Custom MF I believe,
1. Change this MF - remove the input parameter RegistrationForm from the MF.
2. You need to add a "Create Object" activity before "Retrieve Account from Database" in your MF. This will create a new "RegistrationForm" object before associating it to an account retrieved.
Works like a charm now. Thanks Abhishek for the solution and explanation.