.. _2024-02-28-landing-tiles-with-reserved-names-(event_id)_release:

=================================================================================
2024-02-28 - Landing tiles with reserved names (event_id)
=================================================================================

Release
==================
*Status: Preview*

*Type: Bug-Squash*

*Date: 2024-02-28*

Problem
==================
If landing files contained a user attribute called event_id, the patterns to load into history and create rules would fail as event_id is an AgileData.io attribute for tagging every record with a unique event identifier so we can do row level tracking from source to target.

Solution
==================
Now, if the user file contains event_id we alias it as event_id_ to differentiate it from the attribute we add to every table to track every record

Leverage the Magic
====================================
A small tweak to the landing to history jinja template to check for and alias event_id if we see it come through from landing

Last Refreshed
===========================
*Doc Refreshed: 2024-03-01*