[BUG] cannot deploy Import file Activity with destination SMS

[michalchalecki]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When deploying import activity error appears: Internal Server Error.
Import is from Data Extension to All Subscribers list
2023-02-15T15.22.02.406Z.log
ContactSMS_PPD-GL4.importFile-meta.txt

Expected Behavior

Import is successfully deployed.

Steps To Reproduce

1. Move the ContactSMS_PPD-GL4.importFile-meta.json file to directory: deploy/MCREEV/PreProd/importFile
2. Run mcdev deploy MCREEV/PreProd
3. See error "Internal Server Error"

Version

4.3.3

Environment

• OS: Windows 11
• Node: 16.15.0
• npm: 9.3.1

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response

[JoernBerkefeld]

Relevant Log extract:

16:22:13.018 debug: - importFile ContactSMS_PPD-GL4: Import Destination Type SMS not fully supported. Deploy might fail. 
16:22:13.177 debug: undefined 
16:22:13.177 debug: {"documentation":"https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/error-handling.htm","errorcode":0,"message":"Internal Server Error"} 
16:22:13.177 error: ☇ error creating importFile ContactSMS_PPD-GL4 / ContactSMS_PPD-GL4: 
16:22:13.178 debug: Util.signalFataError() sets process.exitCode = 1 
16:22:13.178 error: • Internal Server Error 
16:22:13.178 debug: Util.signalFataError() sets process.exitCode = 1 
16:22:13.179 info: importFile upsert: 0 of 1 created / 0 of 0 updated

[JoernBerkefeld]

the api does not return a value for the target in these cases. it should say "all contacts sms" or sth similar but it doesnt :/

[JoernBerkefeld]

new idea: switch to legacy API?

[JoernBerkefeld]

/legacy/v1/beta/mobile/imports/ seems to get me a list of SMS import definitions - but it's lacking the field mapping and notificationEmailAddress

however, that can then be extended using the returned id to call this endpoint:
/legacy/v1/beta/workers/import/definition/ZFhvUUdwRFhFZW1penhRQzdKVHM4UTo0MTow

[JoernBerkefeld]

for UPSERT there seem to be multiple endpoints, all using POST:

• /legacy/v1/beta/workers/import/definition/
• /legacy/v1/beta/workers/import/definition/{id}/
• /legacy/v1/beta2/workers/import/definition/
• /legacy/v1/workers/import/definition/ OR - /legacy/v1/v1/workers/import/definition/

[JoernBerkefeld]

figured i'd test this despite discovery not mentioning it: the above 4 upsert endpoints do NOT work with GET

[JoernBerkefeld]

the remaining issue seems to be that we don't have a way to resolve the subscriptionDefintionId - which seems to identify the code/keyword combo that's otherwise missing in the response from /legacy/v1/beta/workers/import/definition/ZFhvUUdwRFhFZW1penhRQzdKVHM4UTo0MTow