The error that you see, is saying that you cannot use this field mapping for match-based coupling. This is because Price List code, which is a Code field in Business Central is mapped to a unique id field in Dataverse, which is a GUID. This is one of the non-trivial field mappings that is done in an event subscriber, so you cannot use it for match-based coupling, because match-based coupling is simply setting a filter on it, and that won't work because Guid is not compatible with free text.

The second error that you see is because match-based coupling creates an ad-hoc table mapping (a clone of the main table mapping for price list) and runs on it, and then deletes it after the one-time attempt. Match-based coupling job is a one-time job and cannot be restarted from the job queue entry list, because the on-the fly mapping that is required to run it is deleted.

Making an idea to make this behaviors possible.