Okay, I buy that. Add long as the handler is already doing the needful with regard to whether out not they are blank, which out is, there I'd no need to write them as boilerplate. Go ahead and submit a PR for this.

Dan Smith <notifications@github.com> wrote:

>>      {
>> -        parent::unserialize($simpleFMAdapterRow);
>> +        $this->mapFmFieldOntoProperty('recid', 'recid');
>> +        $this->mapFmFieldOntoProperty('modid', 'modid');
>
>Here is an example of what I was referring to: [FMServer_Sample](https://github.com/dansmith65/SimpleFM_FMServer_Sample/commit/37483f2622dab559143cab19abc6e74b39a561cf) [SimpleFM](https://github.com/dansmith65/SimpleFM/commit/a1bfbd7bad95c733ffbed2c50ed91b220134110f)
>
>My reason is that I can't imagine a scenario where an *entity* would not want to serialize and unserialize recid/modid. I do think you may not want to at run time, like when creating a record, or forcing an update, regardless of modid, but those scenarios have already been covered by your recent changes to the serializeField method.
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/soliantconsulting/SimpleFM_FMServer_Sample/pull/6/files#r3218851