# Show counter dynamc property in "Auto-report format for movement within this map" in Map Window object **URL:** \ **Category:** Module Design\ **Created:** [July 24, 2022, 8:41am UTC](https://forum.vassalengine.org/t/show-counter-dynamc-property-in-auto-report-format-for-movement-within-this-map-in-map-window-object/75089 "2022-07-24T08:41:56Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![marktb1961](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/marktb1961/32/231_2.png) [@marktb1961](https://forum.vassalengine.org/u/marktb1961)\ **Post date:** [February 13, 2023, 12:09pm UTC](https://forum.vassalengine.org/t/show-counter-dynamc-property-in-auto-report-format-for-movement-within-this-map-in-map-window-object/75089/8 "2023-02-13T12:09:06Z")
> [@Brent\_Easton](#): > > Just coming back round to this, there is no reason that an Auto-report format can’t see a DP in a piece and report on it. Country2 won’t appear in the drop-down, but referencing $Country2$ anywhere in the report format should show it. > > Make sure that the piece you where using to test this actually had a value for the Country2 property. Begging to differ, e.g. this Auto-Report format tests various types of normal properties. It looks like only module level GPs are reportable (in addition to the special feature-level properties): `BasicName=$BasicName$ Obscured=$Obscured$ MapGP=$handSide$ CurrentZone=$CurrentZone$ CurrentMap=$CurrentMap$ ModuleVersion=$ModuleVersion$ ModuleGP=$activeSide$` This results in the output for card moved on the map: - BasicName= Obscured= MapGP= CurrentZone= CurrentMap= ModuleVersion=4.3.0a04 ModuleGP=Player 2 I recall it has been discussed before and I thought concluded that map movement auto-reports couldn’t see properties from the piece’s viewpoint. --- _[View the full topic](https://forum.vassalengine.org/t/show-counter-dynamc-property-in-auto-report-format-for-movement-within-this-map-in-map-window-object/75089)._