https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/125610/roadway-designer-not-following-target-aliasingIn my corridor I want one side to tie to existing ground and the other to tie to a proposed surface. In my templates, I have my tie points set to &quot;Project to Surface&quot; and have typed in either &quot;existing&quot; or &quot;proposed&quot; for the value depending on whaten-USTelligent Community 12https://communities.bentley.com/thread/381965?ContentTypeID=1Thu, 01 Sep 2016 23:48:01 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f4ff651f-e478-48de-aa74-b4b0bf496019Marc BachandI agree that the project to surface constraint can not be used with target aliasing. You would want to use an end condition in this case. Project to surface only goes to surface if I remember correctly. I do not use it at all due to inconsistent/unreliable results.<br /> <br /> Marc<div style="clear:both;"></div>https://communities.bentley.com/thread/381962?ContentTypeID=1Thu, 01 Sep 2016 22:56:07 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:28d23f34-db7a-4d6a-9ae3-5e567cc3f611Derek SchmidtI don&#39;t know that target aliasing works in your scenario, using Project to Surface. (I&#39;ve never tried to use it in that application.) It should work for end condition component targets.<br /> <br /> As a quick solution (just to determine as quickly as possible if it works for you), create an end-condition component that seeks &lt;Active&gt; (or whatever label you&#39;re trying to use here, but I guess active) at any slope. That should find whatever is in that alias list. From there, sort out how you can make that work for you.<div style="clear:both;"></div>