# Issue Styling Rooms After Update to Location-Based Properties in Mappedin

**URL:** <https://community.mappedin.com/t/issue-styling-rooms-after-update-to-location-based-properties-in-mappedin/273>\
**Category:** Map Making\
**Created:** [April 16, 2025, 4:45am UTC](https://community.mappedin.com/t/issue-styling-rooms-after-update-to-location-based-properties-in-mappedin/273 "2025-04-16T04:45:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manikandan](https://avatars.discourse-cdn.com/v4/letter/m/3da27b/32.png) [@Manikandan](https://community.mappedin.com/u/Manikandan)\
**Post date:** [April 16, 2025, 4:45am UTC](https://community.mappedin.com/t/issue-styling-rooms-after-update-to-location-based-properties-in-mappedin/273/1 "2025-04-16T04:45:01Z")

</div>

Previously, we used the `space` (room) feature in Mappedin to add name and detail properties for each room. Based on those room names, we applied custom styles in the code—such as colors, text labels, etc.

However, after the recent update, Mappedin introduced a new `location` feature where we now have to fill in the name, description, and other details under `location` instead of the `room` (space) directly.

Because of this change, our existing room-based properties and styling logic no longer work. How can we now reference or style the rooms based on the new `location` data? Is there a recommended way to migrate or map the old room data to the new location structure to preserve our existing styles?

Looking for guidance on how to apply styles dynamically using the new `location` details.

Thanks!

---

<div class="post-metadata">

**Author:** ![msohm](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.mappedin.com/msohm/32/6_2.png) [@msohm](https://community.mappedin.com/u/msohm)\
**Post date:** [April 16, 2025, 2:30pm UTC](https://community.mappedin.com/t/issue-styling-rooms-after-update-to-location-based-properties-in-mappedin/273/2 "2025-04-16T14:30:29Z")

</div>

Hi Manikandan,

Update to the latest version of Mappedin JS and your existing logic should still work. It has support to map data from the new location feature to `Space` fields like `space.name` and `space.description` that you are already using.

It also supports getting all of the new location fields as well if you start to use those.

Once the map is “updated” to use the new Location features, a Mappedin JS upgrade is required (the Map Editor will prompt to warn of this).

---

<div class="post-metadata">

**Author:** ![Manikandan](https://avatars.discourse-cdn.com/v4/letter/m/3da27b/32.png) [@Manikandan](https://community.mappedin.com/u/Manikandan)\
**Post date:** [April 17, 2025, 5:35am UTC](https://community.mappedin.com/t/issue-styling-rooms-after-update-to-location-based-properties-in-mappedin/273/4 "2025-04-17T05:35:45Z")

</div>

Hi,

Thanks for the quick support!

I’ve updated to the latest version of Mappedin JS, and everything is working perfectly now. Our existing logic is picking up the location data as expected, and the styles are being applied correctly.

Appreciate the guidance!