Feature/cmg 774

[aishwarya-cstk]

JIRA ticeket:
[https://contentstack.atlassian.net/browse/CMG-1114]

📋 PR Type

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

---

📝 Description

What changed?

• Fixed processFieldByType's file and reference cases in api/src/services/drupal/entries.service.ts.

• Added handling for values that are already resolved into asset/reference objects identified by a .uid.

• Already-resolved objects are now passed through as-is instead of attempting to derive:

  • assets_${value}
  • content_type_entries_title_${value}

• Applied the fix to both single-value and multiple array branches.

Why?

Drupal image/file fields such as field_image_target_id were being resolved twice:

1. processFieldData correctly resolves the raw target_id into a Contentstack asset reference object.
2. The already-resolved object is then passed to processFieldByType's file case, which assumes the value is still a raw numeric ID.
3. The code attempts to look up the object as assets_[object Object].
4. The lookup fails, causing the field to be silently removed from the migrated entry.

As a result, field_image and other asset/reference fields resolved earlier in the migration pipeline were missing from the final migrated entry.

Fix

The fix short-circuits processing when the value is already a resolved object containing a .uid.

This is additive and does not change the existing raw-ID flow, including:

• Numeric asset/reference IDs
• Comma-separated GROUP_CONCAT arrays
• Missing-asset error handling
• Existing reference resolution logic

The fix also works correctly for delta re-runs because Drupal entries are fully re-fetched and re-processed on every migration run rather than incrementally patched.

---

🧩 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. Run a Drupal migration against a content type containing:

   • An image/file field such as field_image
   • At least one entity/reference field

2. Inspect the generated entry JSON under:
   data/<stack_id>/entries/<content_type>/<locale>/<locale>.json

3. Confirm that the image/file and reference fields are present in the generated entry.

4. Verify that the fields contain valid Contentstack uid references.

5. Re-run the same migration as a second iteration/delta run.

6. Confirm that the fields remain present and correctly resolved after the second run.

7. Verify that no "Asset ... not found or invalid, removing field" errors are logged for valid assets.

Expected Result

field_image and other asset/reference fields should:

• Be present in the final migrated entry.
• Contain the correct Contentstack asset/entry UID.
• Work correctly on both the initial migration and subsequent delta re-runs.
• Not generate "Asset ... not found or invalid, removing field" errors for valid assets.

---

📸 Screenshots / Recordings

Before	After
N/A — backend field-mapping fix	N/A — backend field-mapping fix

---

🔗 Related PRs / Dependencies

• N/A

---

✅ Author Checklist

Complete this before moving the PR out of Draft.

• Branch follows naming convention: feature/, bugfix/, or hotfix/ + 5–30 lowercase characters
• 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 / documentation updated if behavior changed
• Talisman pre-push scan passes with no secrets flagged

---

👀 Reviewer Notes

• The guard relies on the presence of .uid to identify an already-resolved asset/reference object.

• The .uid field is always set when asset references are constructed in api/src/services/drupal/assets.service.ts.

• Please flag if there is any known resolved-object shape that does not contain .uid.

• No automated test was added directly to the existing test suite because api/src/services/drupal currently does not have field-processing unit tests to extend.

• The fix was manually verified using a standalone script covering both:

  • A first migration run
  • A second/delta migration run

• A Vitest unit test for processFieldByType can be added if required.

---

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

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[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	0	0	10	✅ Passed
🟠 High Severity	15	378	25	✅ Passed
🟡 Medium Severity	19	11	500	✅ Passed
🔵 Low Severity	2	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	371	30 / 120 days	⚠️ Warning
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 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: 378
• Medium without fixes: 11
• Low without fixes: 0

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

Consider reviewing these vulnerabilities when fixes become available.