# pyResourcePath does not substitute actual values from Params after upgrading to 8.7.3 from 7.3.1

**URL:** <https://forums.pega.com/t/pyresourcepath-does-not-substitute-actual-values-from-params-after-upgrading-to-8-7-3-from-7-3-1/4253>\
**Category:** General\
**Tags:** government, 8-7-3, data-integration, lead-system-architect\
**Created:** [March 29, 2023, 7:38pm UTC](https://forums.pega.com/t/pyresourcepath-does-not-substitute-actual-values-from-params-after-upgrading-to-8-7-3-from-7-3-1/4253 "2023-03-29T19:38:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![KOMARINA](https://avatars.discourse-cdn.com/v4/letter/k/df788c/32.png) [@KOMARINA](https://forums.pega.com/u/KOMARINA)\
**Post date:** [March 29, 2023, 7:38pm UTC](https://forums.pega.com/t/pyresourcepath-does-not-substitute-actual-values-from-params-after-upgrading-to-8-7-3-from-7-3-1/4253/1 "2023-03-29T19:38:39Z")

</div>

Hi,

Greetings. Hope you are all well! We recenlty upgraded from Pega 7.3.1 to Pega 8.7.3 and all our connect rules are using references like {endpoint}/{referenceValue} within Resource Path of a connect rule and substituted via Map from Clipboard

endpoint = DataPage.endpoint(TEST)

referenceValue = Param.referenceValue

We were using this ResourcePath in a data table to record the Connect calls for debugging and performance. In Pega 7.3.1, I can see the values are substituted as [https://url/1234566](https://url/1234566) however in Pega 8.7.3, I see this as {endpoint}/{referenceValue}.

We cannot upgrade to new endpoint configuration now as this is a 6 year old application and changing this will have implications to business.

Can someone please let me know if there is any other way to get the actual ResourcePath?

Regards,

Bharat

---

<div class="post-metadata">

**Author:** ![KOMARINA](https://avatars.discourse-cdn.com/v4/letter/k/df788c/32.png) [@KOMARINA](https://forums.pega.com/u/KOMARINA)\
**Post date:** [November 13, 2023, 7:25pm UTC](https://forums.pega.com/t/pyresourcepath-does-not-substitute-actual-values-from-params-after-upgrading-to-8-7-3-from-7-3-1/4253/2 "2023-11-13T19:25:20Z")

</div>

We added a workaround to pass individual param values along with the complete endpoint

example: {endpoint}{identifier} {endpoint = [.xyz Domain Names | Join Generation XYZ](https://xyz.com/b), identifier = 1}

Regards,

Bharat