# Data and list views in modeling don't work when filenames contain dots

**URL:** <https://community.holistics.io/t/data-and-list-views-in-modeling-dont-work-when-filenames-contain-dots/1910>\
**Category:** Report Bugs\
**Created:** [April 22, 2024, 7:59pm UTC](https://community.holistics.io/t/data-and-list-views-in-modeling-dont-work-when-filenames-contain-dots/1910 "2024-04-22T19:59:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dacou](https://community.holistics.io/user_avatar/community.holistics.io/dacou/32/467_2.png) [@dacou](https://community.holistics.io/u/dacou)\
**Post date:** [April 22, 2024, 7:59pm UTC](https://community.holistics.io/t/data-and-list-views-in-modeling-dont-work-when-filenames-contain-dots/1910/1 "2024-04-22T19:59:39Z")

</div>

We took the habit to name query models like this : `model_name.trans.model.aml`.  
This allows us to find them more easily.

But for those files the `data` and `list` tabs are left empty. We have to remove the dot in the filename like here : `model_name-trans.model.aml`.

---

<div class="post-metadata">

**Author:** ![thanh](https://community.holistics.io/user_avatar/community.holistics.io/thanh/32/53_2.png) [@thanh](https://community.holistics.io/u/thanh)\
**Post date:** [April 23, 2024, 3:31am UTC](https://community.holistics.io/t/data-and-list-views-in-modeling-dont-work-when-filenames-contain-dots/1910/2 "2024-04-23T03:31:07Z")

</div>

Hi Damien,

After checking internally with our team, our current logic to detect a model AML file is to check the extension which includes everything after the first dot e.g. `trans.model.aml` in your case. This is indeed less flexible than ideal and we have added the improvement to only consider the last 2 dots to our backlog.

Thanks again for raising this up to us!
