@Andrew88
@Andrew88 wrote:
Thank you for the reply. I already read about this function, but unfortunately can't find any samples/scenarios in documentation on how to use it with the form's data.
Then you can check this specific example. It is being modeled with two SharePoint Lists but it can be applied with two Dataverse Tables as well.
First, make sure that if you use multiple Forms, that their DefaultMode is set to FormMode.New for both of them
Then, the main task would be to match up Controls with the right values in them, with columns from the data source. In an example of a SharePoint List set up as follows:
and yet another SharePoint List set up as follows:
and presuming two SharePoint List Data Sources set up correctly in the app:
and as mentioned, also presuming two Forms with FormMode.New as the DefaultMode on both forms,
and finally, presuming one button - you would put something like this in the OnSelect of that button to save the records to different tables:
Patch(Employee,{'Title': DataCardValue1.Text,'Employee Name':DataCardValue3.Text,'Employee Code':DataCardValue2.Text});
Patch(OnBoarding,{'Title': DataCardValue5.Text,'OnBoarding Comment':DataCardValue6.Text});
If your data source requires any columns as a business rule or otherwise on the server side somehow, those MUST be provided in the Patch function or you may get error in runtime. In our example, the Title field of SharePoint list is always required on the data source level, so we must provide it, or we do get a runtime error in our case if we were to omit this from either Patch function. In Dataverse this also may apply to any Table where any columns are marked as Business Required on them - for those the columns may have to be possibly specified and provided with a value in the Patch function.
You can see it working in the following graphic example below as well:
Check if something like the above helps.
