The "Project funding source" data entity (staging table ProjFundingSourceStaging) seems to require the "PartyNumber" field populating, reporting the error message below when a DMF import project does not include a value:

"Results. The party ID specified does not exist. Results. validateWrite failed on data source 'ProjFundingSource (ProjFundingSource)'"

But then for records where the "FundingType" field is "Customer", it doesn't use that "PartyNumber" field for the customer lookup, but instead uses the "CustomerOrganization" field. I appreciate the validateWrite method above is on the ProjFundingSource table which will be reached through code paths other than the data entity, but I believe that just means the data entity/DMF should handle the scenario earlier, i.e. by using the Party ID for the customer.

Demonstration process:

1. Ensure you have two customers, and identify their customer number & party number
2. Ensure you have a project contract created
3. Create a DMF input file for the Project funding source data entity specifying the project contract above & the customer number for one customer in the CustomerOrganization field and the party number for the other customer in PartyNumber
4. Import through DMF
5. Review the project contract
6. Observe that the funding source added has used the CustomerOrganization field for the associated customer
7. Create a copy of DMF input file, modifying it by removing the PartyNumber and changing the FundingSourceID
8. Import through DMF
9. Observe error The party ID specified does not exist. even though DMF isn’t going to use the party ID in question