Signals Notebook: Issue with Managing Hierarchical Attribute Post 500-Value Limitation

With our recent release, a limit of 500 entries has been introduced when creating attribute lists via the UI. This change was implemented to avoid performance issues and delays often encountered with larger datasets

1. Exporting Attribute List via API:
   You can retrieve the complete list of attribute values using the API endpoint GET /attributes/{eid}. This is especially helpful in scenarios where the list exceeds 500 entries and the UI no longer displays all values due to recent version updates. 

2. Updating the Attribute List: The attribute list can be updated using the following methods:

   1. Via User Interface (UI):
      Users can conveniently update the list through the CSV upload option available within the application’s UI. This method is ideal for bulk updates and requires minimal technical effort.

   2. Via API Integration:
      For more programmatic control, the attribute list can also be updated using the API. Specifically, the PATCH /attributes/{eid} endpoint allows you to modify the attribute content dynamically, enabling seamless integration with automated workflows.