<?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: Service Catalog - Sc_REQ table - how to differentiate  REQs from different service catalogs in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3468992#M5846</link>
    <description>&lt;P&gt;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/349783"&gt;@MThomas1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You cannot show catalog item name in list/form of your sc_request.&lt;/P&gt;
&lt;P&gt;You need to create a &lt;STRONG&gt;database view&lt;/STRONG&gt; with sc_request and sc_req_item for that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If your logic is in a script that runs on sc_request then you can make a gliderecord call to sc_req_item to get the catalog item name.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Rename REQ number is a recommended option? - &lt;STRONG&gt;Definitely NOT Recommended&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Accept the solution and mark as helpful if it does, to benefit future readers.&lt;BR /&gt;Regards,&lt;BR /&gt;Sumanth&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 16 Jan 2026 17:36:04 GMT</pubDate>
    <dc:creator>SumanthDosapati</dc:creator>
    <dc:date>2026-01-16T17:36:04Z</dc:date>
    <item>
      <title>Service Catalog - Sc_REQ table - how to differentiate  REQs from different service catalogs</title>
      <link>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3468937#M5845</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we have 1 service catalog for access requests - which creates REQ/RITM/SCTASKS.&lt;/P&gt;&lt;P&gt;we are in need of creating another catalog for license request purpose.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since both the REQs will be created in sc_request table with number "REQ0000000" format,&amp;nbsp; how can we differentiate 2 different catalogs requests for reporting/matrix purpose in the sc_request table ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rename REQ number is a recommended option?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any OOTB options available?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jan 2026 16:49:50 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3468937#M5845</guid>
      <dc:creator>MThomas1</dc:creator>
      <dc:date>2026-01-16T16:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Service Catalog - Sc_REQ table - how to differentiate  REQs from different service catalogs</title>
      <link>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3468992#M5846</link>
      <description>&lt;P&gt;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/349783"&gt;@MThomas1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You cannot show catalog item name in list/form of your sc_request.&lt;/P&gt;
&lt;P&gt;You need to create a &lt;STRONG&gt;database view&lt;/STRONG&gt; with sc_request and sc_req_item for that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If your logic is in a script that runs on sc_request then you can make a gliderecord call to sc_req_item to get the catalog item name.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Rename REQ number is a recommended option? - &lt;STRONG&gt;Definitely NOT Recommended&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Accept the solution and mark as helpful if it does, to benefit future readers.&lt;BR /&gt;Regards,&lt;BR /&gt;Sumanth&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jan 2026 17:36:04 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3468992#M5846</guid>
      <dc:creator>SumanthDosapati</dc:creator>
      <dc:date>2026-01-16T17:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: Service Catalog - Sc_REQ table - how to differentiate  REQs from different service catalogs</title>
      <link>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3469004#M5847</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/349783"&gt;@MThomas1&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;!-- StartFragment  --&gt;&lt;/P&gt;&lt;P&gt;if your goal is reporting/matrix separation, the cleanest OOTB solution is to report by catalog or category rather than touching the REQ number.&lt;/P&gt;&lt;P&gt;&lt;!-- EndFragment  --&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jan 2026 17:46:43 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3469004#M5847</guid>
      <dc:creator>yashkamde</dc:creator>
      <dc:date>2026-01-16T17:46:43Z</dc:date>
    </item>
    <item>
      <title>Re: Service Catalog - Sc_REQ table - how to differentiate  REQs from different service catalogs</title>
      <link>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3469785#M5851</link>
      <description>&lt;P&gt;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/349783"&gt;@MThomas1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Did the above solution solve your query? If yes, Accept the solution and mark as helpful to close the thread and benefit other readers.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sumanth&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 10:06:56 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3469785#M5851</guid>
      <dc:creator>SumanthDosapati</dc:creator>
      <dc:date>2026-01-19T10:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: Service Catalog - Sc_REQ table - how to differentiate  REQs from different service catalogs</title>
      <link>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3469802#M5852</link>
      <description>&lt;P&gt;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/349783"&gt;@MThomas1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I agree with what&amp;nbsp;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/347849"&gt;@SumanthDosapati&lt;/a&gt;&amp;nbsp; mentioned.&lt;/P&gt;
&lt;P&gt;that's the way forward&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":light_bulb:"&gt;💡&lt;/span&gt; If my response helped, please mark it as correct &lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; and close the thread &lt;span class="lia-unicode-emoji" title=":locked:"&gt;🔒&lt;/span&gt;— this helps future readers find the solution faster! &lt;span class="lia-unicode-emoji" title=":folded_hands:"&gt;🙏&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 10:22:08 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/service-catalog-sc-req-table-how-to-differentiate-reqs-from/m-p/3469802#M5852</guid>
      <dc:creator>Ankur Bawiskar</dc:creator>
      <dc:date>2026-01-19T10:22:08Z</dc:date>
    </item>
  </channel>
</rss>

