Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Seed address + prefix

Milan_Vucetic
Community Advisor
Community Advisor

Hi all,

 

we have issues with sending delivery to seed addresses which contains a plus (+) prefix.

Seed schema is extended and number is stored and shown properly (without +) in the forms but after delivery execution + is added and sendout to that number is failed.

milanv69354962_0-1579080423602.png

This is the schema extension:

milanv69354962_1-1579080566420.png

Any idea?

 

Regards,

Milan

1 Accepted Solution
Amit_Kumar
Correct answer by
Community Advisor
Community Advisor

Another option would be:

You can create a new field like newPhoneNumber and update target mapping to use that new field for sms.

 

FYI:

To delete an existing attribute on factory schemas follow the steps outlined here

  • Extend the scehma
  • Define the same attribute again in this extended schema (name must match) and then define _operation="delete"
  • Save the schema and update database structure.

<attribute name="attributename" _operation="delete"/>

 

Regards,

Amit

View solution in original post

3 Replies
Amit_Kumar
Community Advisor
Community Advisor

Hi Milan,

This is happening because of your ootb data policy for the mobile phone. You have to add a new field in the recipient for mobile phone and update the target mapping to disable this behaviour. 

Alternatively: 

Did you uncheck the following checkbox in the connector?

 

Amit_Kumar_0-1579173562051.png

 

anyone of these two will fix your issue.

 

Regards,

Amit

Milan_Vucetic
Community Advisor
Community Advisor

Hi Amit,

I would avoid first option and second option is not available as we use a custom connector. I saw that is possible to edit default (locked) schema but not sure how to do it. Aware that is not recommended but this is really annoying problem because of one small "not-extensible" data policy 🙂 There must be some easier workaround.

Any other idea? Thank you in advance.

Regards,
Milan

Amit_Kumar
Correct answer by
Community Advisor
Community Advisor

Another option would be:

You can create a new field like newPhoneNumber and update target mapping to use that new field for sms.

 

FYI:

To delete an existing attribute on factory schemas follow the steps outlined here

  • Extend the scehma
  • Define the same attribute again in this extended schema (name must match) and then define _operation="delete"
  • Save the schema and update database structure.

<attribute name="attributename" _operation="delete"/>

 

Regards,

Amit

View solution in original post