Data too long for column 'salesforce_mapping'

Created on 30 January 2019, almost 6 years ago
Updated 27 June 2023, over 1 year ago

Problem/Motivation

When creating a mapping, the form allows for a mapping ID/machine name up to 255 characters in length. But, when creating a mapped object, which references a mapping by ID/machine-name, the salesforce_mapping field in the DB only accepts a maximum of 32 characters.

So, if your mapping's machine name/ID is over 32-characters in length, you cannot save Mapped Objects for data it pulls down, due to a "Data too long for column 'salesforce_mapping'" error on MO save.

Proposed resolution

OR

Drop the max-length of the salesforce mapping ID/machine name to 32-characters.

Remaining tasks

-
-
- Review

User interface changes

A reduced mapping machine name length limit in the new mapping and edit mapping forms.

API changes

None.

Data model changes

None.

Release notes snippet

TBD

πŸ› Bug report
Status

Fixed

Version

3.0

Component

salesforce_mapping.module

Created by

πŸ‡ΊπŸ‡ΈUnited States chrisolof

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States bwoods

    Just in case anyone is still seeing this, I noticed the same error message in my logs recently. Apparently in my case, the issue is that I have a single Webform submission that creates multiple SF records. On return, only one SF record can be mapped to the Webform submission. The error doesn't seem to have any effect on the actual SF records creation.

Production build 0.71.5 2024