SharePoint Structure Dependencies with P&D

Key Point:

• Match SharePoint Structure Between Development and Production: To ensure seamless deployment of K2 solutions, maintain identical SharePoint site structures for lists used in the solution across both environments.

Scenario:

• Production Structure:

  • Root Site
    • List A
    • Subsite
      • List B

• Development Structure (Incorrect):

  • Root Site
    • List A
    • List B
    • Subsite

Deployment Issue:

• Attempting to deploy a package (.kspx) created in the incorrect Development structure to Production will fail to map List B correctly, as the package expects it under the root site, not in a subsite.

Solutions:

• Preventive:
  • Replicate the Production structure in Development precisely.
• Reactive:
  • Recreate and Remap: Delete and recreate List B SmartObjects in Development to match the Production structure.
  • Move List B in Production: Relocate List B's template and data in Production to align with the Development structure (less ideal due to potential data loss or disruption).

Takeaway:

• Prioritize Structure Consistency: Always maintain consistent SharePoint structures for lists involved in K2 solutions across development and production environments to avoid deployment issues and ensure smooth solution transitions.