The input “Records” must refer to record types with data sync enabled that use a database as the source. Received (*The record Type Name which is related to the the record given in Input)

In the Write Records version released in 23.3 (writing records with related records) you would get this error if any records in your variable are of a different data source than your base record, or if your base record is not a record type with data sync enabled from a database source. This constraint will be relaxed in 24.1 to ignore the different data source records, but until then these are the situations where you could expect to receive this error. 

Would it be possible to make that error message a bit more expressive? Your explanation is great, but the error message does not point in that direction.

Yes, I can how this could be misleading. It will be applicable in 24.1, but for previous releases we can add more explanation of this error in the Write Records documentation. 

In 24.1 and 24.2, will relaxing the constraint to ignore different data source records result in the error message not appearing as well as the record relationship being maintained appropriately, or will ignoring different data source records mean that record relationships cannot be maintained between records with different data sources?

For additional context, our dev environment is on 23.4. We're getting errors when trying to write Synced Records when they have a relationship with a Record with a different Data Source. We're trying to implement a workaround but our environment will be updated soon to 24.2. When attempting to do a workaround, however, I've encountered this error in the writeRecord smart service process node: 

The input "Records" cannot insert or update a record which is referring to different referenced records via relatedRecordId at the same time. To create a reference to a related record, include either a relationship reference or the required common field value for "relatedRecordId". Location of conflicting changes: (our record name)	

relatedRecordId is the name of the field that the record relationship is based on in our base record. This error message makes it sound like even if the constraint is relaxed that record relationships might not be maintained if the relationship reference cannot be included in the write

For additional context, our dev environment is on 23.4. We're getting errors when trying to write Synced Records when they have a relationship with a Record with a different Data Source. We're trying to implement a workaround but our environment will be updated soon to 24.2. When attempting to do a workaround, however, I've encountered this error in the writeRecord smart service process node: 

The input "Records" cannot insert or update a record which is referring to different referenced records via relatedRecordId at the same time. To create a reference to a related record, include either a relationship reference or the required common field value for "relatedRecordId". Location of conflicting changes: (our record name)	

relatedRecordId is the name of the field that the record relationship is based on in our base record. This error message makes it sound like even if the constraint is relaxed that record relationships might not be maintained if the relationship reference cannot be included in the write