# Client tags not shown when working in the Project Library

**URL:** <https://forum.inductiveautomation.com/t/client-tags-not-shown-when-working-in-the-project-library/107059>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [June 4, 2025, 9:08pm UTC](https://forum.inductiveautomation.com/t/client-tags-not-shown-when-working-in-the-project-library/107059 "2025-06-04T21:08:00Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Check](https://avatars.discourse-cdn.com/v4/letter/c/e19adc/32.png) [@Check](https://forum.inductiveautomation.com/u/Check)\
**Post date:** [June 4, 2025, 10:39pm UTC](https://forum.inductiveautomation.com/t/client-tags-not-shown-when-working-in-the-project-library/107059/5 "2025-06-04T22:39:52Z")

</div>

In my packing application, the user enters the order number, and Ignition calls a stored procedure to retrieve the order data. About 10 tags are populated with the results. The user then makes a few selections on the screen, which update a few more tags. When they click a button to complete packing, it calls a function in the Project Library that reads these tag values to build a dictionary and send it as a payload to an EWM API.

Given this setup, would it be a good practice to pass all 14 values as arguments to the function? Or is there a better way to handle this?

---

_[View the full topic](https://forum.inductiveautomation.com/t/client-tags-not-shown-when-working-in-the-project-library/107059)._
