fix: update sourceType assignment in contentTypeMapper for droplist c…

[aishwarya-cstk]

Dropdown field exported GUID value | Dropdown field exports actual selected value

🔗 Jira Ticket

[CMG-1006](https://contentstack.atlassian.net/browse/CMG-1006)

---

📋 PR Type

• ✨ Feature
• 🐛 Bug Fix
• 🔥 Hotfix
• ♻️ Refactor
• 🧹 Chore / Dependency Update
• 📝 Documentation

---

📝 Description

What changed?

• Fixed an issue in Delta Migration export where dropdown fields were exporting GUID values instead of the actual selected option values.
• Updated the export logic to resolve and export the corresponding dropdown option value.
• Ensured exported data remains consistent with the values displayed in Contentstack entries.

Why?

When exporting entries through Delta Migration, dropdown fields were incorrectly exporting internal GUID identifiers rather than the actual option values selected by users. This resulted in inaccurate export data and created confusion during migration validation and data verification processes.

This fix ensures that the exported output contains the expected dropdown values, making the migration data readable and accurate.

---

🧩 Affected Areas

• [] api — Node.js backend
• ui — React frontend
• upload-api — Upload API server
• docker / docker-compose
• CI / GitHub Actions workflows
• Environment variables / config
• Other:

---

🧪 How to Test

1. Create or identify a content type containing a dropdown field.
2. Create/update an entry and select a dropdown option.
3. Run Delta Migration export for the entry.
4. Verify the exported JSON/data for the dropdown field.

Expected result:

• The exported data should contain the actual dropdown option value.
• GUID/internal identifiers should not be exported for dropdown fields.
• Existing export functionality should continue to work without regression.

---

📸 Screenshots / Recordings

Before	After
Dropdown field exported GUID value	Dropdown field exports actual selected value

---

🔗 Related PRs / Dependencies

• N/A

---

✅ Author Checklist

• Branch follows naming convention: feature/, bugfix/, or hotfix/ + 5–30 lowercase chars
• Jira ticket linked above
• Self-reviewed the diff — no debug logs, commented-out code, or TODOs left in
• .env / example.env updated if new environment variables were added
• No sensitive credentials or secrets committed
• Existing tests pass locally (npm test)
• New tests written (or not applicable — explain why)
• README.md / docs updated if behaviour changed
• Talisman pre-push scan passes (no secrets flagged)

---

👀 Reviewer Notes

Please focus on:

• Dropdown field export logic.
• Validation of exported values across different dropdown configurations.
• Regression testing for other field types to ensure existing export behavior remains unchanged.

---

Migration v2 · Docs: https://github.com/contentstack/migration-v2#readme · Issues: https://github.com/contentstack/migration-v2/issues

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	1	0	10	✅ Passed
🟠 High Severity	14	341	25	✅ Passed
🟡 Medium Severity	36	2	500	✅ Passed
🔵 Low Severity	1	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	2	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 341
• Medium without fixes: 2
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	1	0	10	✅ Passed
🟠 High Severity	14	341	25	✅ Passed
🟡 Medium Severity	36	2	500	✅ Passed
🔵 Low Severity	1	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	2	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 341
• Medium without fixes: 2
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.