# Alarm Pipline Expression

**URL:** <https://forum.inductiveautomation.com/t/alarm-pipline-expression/93794>\
**Category:** Ignition\
**Created:** [July 26, 2024, 2:26pm UTC](https://forum.inductiveautomation.com/t/alarm-pipline-expression/93794 "2024-07-26T14:26:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\
**Post date:** [July 26, 2024, 3:43pm UTC](https://forum.inductiveautomation.com/t/alarm-pipline-expression/93794/2 "2024-07-26T15:43:46Z")

</div>

This port seems promising:

> [@Alarm pipeline binding](https://forum.inductiveautomation.com/t/alarm-pipeline-binding/45871/9):
>
> We have multiple projects on the same gateway with the same standard tag provider. Here is what I have come up with… Within the Tag Browser, have one folder for each project. The names of these top-level folders match the names of the projects. For alarms, bind the Active Pipeline to split({PathToTag}, '/')[0,0] + '/pipeline name'.

---

_[View the full topic](https://forum.inductiveautomation.com/t/alarm-pipline-expression/93794)._