I'm still seeing issues. From what I can tell, the Expression generator appears to be correctly reading the @atlas_feature variable now, and in fact most references in the Reports are working correctly. However, my attribute tables are still empty on the Reports page. I'll file a bug report to see if we can get to the bottom of it.
On Mon, Feb 11, 2019 at 8:47 PM Nyall Dawson <[email protected]> wrote: > On Tue, 12 Feb 2019 at 09:59, Spencer Gardner <[email protected]> > wrote: > > > > I have a map document set up with a report that filters an attribute > table based on an attribute in the layers used for filtering (i.e. the > "atlas" layer for lack of a better Reports-oriented term). In 3.4.2 I could > use the @atlas_feature variable to grab the attribute I needed, but I've > discovered this doesn't work in 3.4.4. Was there a change to the handling > of @atlas_feature between the two versions? If so, I'll file a bug report. > Otherwise, I'm at a loss as to what's going on. > > > > That's an unfortunate bug in 3.4.4 - it's fixed for next weeks 3.4.5 > release. > > Nyall > > > > Thanks! > > Spencer > > _______________________________________________ > > QGIS-Developer mailing list > > [email protected] > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
