Thanks for raising this. I work on the product side of Data Sync and am the author of the Outlook listing. I made a mistake by referencing an older mappings file that did allow us to confidently map that 'company name' field in the set of default field mappings (PieSync) - but in the Data Sync world it is functioning slightly differently. The one big difference being that company name which in Data Sync can be mapped, but it needs to be explicitly 'custom' mapped which is only available on Starter.
For now I've went ahead and aligned the field mappings on the marketplace listing, with the field mappings that you actually get while setting up a sync.
So while I've just rectified the documentation - it's probably not the solution you were hoping for. I agree with you that company name ideally should sit in the free tier. Please trust me in that this was not an intentional and commercial omission. Rather, it is a functional side effect of us wanting to also support company object syncing in the future.
Again, thank you for raising this, and I will commit to finding a solution 🙂
@bsm007 This is now fixed - we've added the associated company name in the default field mapping. If you had a sync running, you do need to go in and turn it off and on again for the change to take effect.
@MiaSrebrnjak You are correct that Company Name SHOULD be mapped according to the documentation on that page, but it is not. I have attached a screen shot of my actual mapping - it is not included.
Thanks for raising this. I work on the product side of Data Sync and am the author of the Outlook listing. I made a mistake by referencing an older mappings file that did allow us to confidently map that 'company name' field in the set of default field mappings (PieSync) - but in the Data Sync world it is functioning slightly differently. The one big difference being that company name which in Data Sync can be mapped, but it needs to be explicitly 'custom' mapped which is only available on Starter.
For now I've went ahead and aligned the field mappings on the marketplace listing, with the field mappings that you actually get while setting up a sync.
So while I've just rectified the documentation - it's probably not the solution you were hoping for. I agree with you that company name ideally should sit in the free tier. Please trust me in that this was not an intentional and commercial omission. Rather, it is a functional side effect of us wanting to also support company object syncing in the future.
Again, thank you for raising this, and I will commit to finding a solution 🙂
@FransLeys Thank you for clarifying and commiting to finding a solution. Yes, the Company Name field is critical for a CRM and should be included in the default mapping. Not sure I understand why it needs to be 'custom' mapped.
@bsm007 This is now fixed - we've added the associated company name in the default field mapping. If you had a sync running, you do need to go in and turn it off and on again for the change to take effect.