<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Manifest json for SAP Commerce Cloud -Environment specific properties in CRM and CX Q&amp;A</title>
    <link>https://community.sap.com/t5/crm-and-cx-q-a/manifest-json-for-sap-commerce-cloud-environment-specific-properties/qaa-p/12311643#M427715</link>
    <description>&lt;P&gt;HI, Did you find any solution for this?&lt;/P&gt;</description>
    <pubDate>Fri, 17 Sep 2021 00:00:30 GMT</pubDate>
    <dc:creator>former_member736016</dc:creator>
    <dc:date>2021-09-17T00:00:30Z</dc:date>
    <item>
      <title>Manifest json for SAP Commerce Cloud -Environment specific properties</title>
      <link>https://community.sap.com/t5/crm-and-cx-q-a/manifest-json-for-sap-commerce-cloud-environment-specific-properties/qaq-p/12311642</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
  &lt;P&gt; Can anyone suggest a way on how to configure the manifest file for SAP Commerce Cloud for multiple environments sharing the same persona. Eg: two environments p1 and p2 with same persona as production . Also we want to separate the properties per aspect of the environment.&lt;/P&gt;
  &lt;P&gt;Tried creating a property file as hcs_accstorefront_p2.properties .There was no issue during the build and deployment process but the configured properties in the file did not override the persona specific property defined in manifest. Is there some other file naming convention for the same. The newly created file was placed parallel to the manifest json in folder structure.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Mar 2021 10:28:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/crm-and-cx-q-a/manifest-json-for-sap-commerce-cloud-environment-specific-properties/qaq-p/12311642</guid>
      <dc:creator>former_member656161</dc:creator>
      <dc:date>2021-03-18T10:28:16Z</dc:date>
    </item>
    <item>
      <title>Re: Manifest json for SAP Commerce Cloud -Environment specific properties</title>
      <link>https://community.sap.com/t5/crm-and-cx-q-a/manifest-json-for-sap-commerce-cloud-environment-specific-properties/qaa-p/12311643#M427715</link>
      <description>&lt;P&gt;HI, Did you find any solution for this?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Sep 2021 00:00:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/crm-and-cx-q-a/manifest-json-for-sap-commerce-cloud-environment-specific-properties/qaa-p/12311643#M427715</guid>
      <dc:creator>former_member736016</dc:creator>
      <dc:date>2021-09-17T00:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: Manifest json for SAP Commerce Cloud -Environment specific properties</title>
      <link>https://community.sap.com/t5/crm-and-cx-q-a/manifest-json-for-sap-commerce-cloud-environment-specific-properties/qaa-p/12311644#M427716</link>
      <description>&lt;P&gt;Hi Varun,&lt;/P&gt;&lt;P&gt;Currently ,the only way to configure properties for different environments sharing same persona for different aspects is to define them through commerce cloud portal for one of them (if there are two with same persona).&lt;/P&gt;&lt;P&gt;1. For common properties to be applied across all aspects either mention under Services-&amp;gt; hcs_common-&amp;gt;properties  on the portal or create a file  hcs_common_{environment}.properties parallel to manifest.json in code.&lt;/P&gt;&lt;P&gt; 2. For aspect related properties mention under Properties tab for the  specific service on cloud portal.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Sep 2021 08:03:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/crm-and-cx-q-a/manifest-json-for-sap-commerce-cloud-environment-specific-properties/qaa-p/12311644#M427716</guid>
      <dc:creator>former_member656161</dc:creator>
      <dc:date>2021-09-18T08:03:32Z</dc:date>
    </item>
  </channel>
</rss>

