{"id":7884,"date":"2011-09-23t16:42:28","date_gmt":"2011-09-23t20:42:28","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=163"},"modified":"2019-10-09t14:06:58","modified_gmt":"2019-10-09t18:06:58","slug":"primavera-p6-filters-export-excel","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/primavera-p6-filters-export-excel\/","title":{"rendered":"using primavera p6 filters on export to excel"},"content":{"rendered":"
primavera’s custom activity filters<\/a> are great for focusing in on a subcontractor’s work list or even to hide activities that are already completed. \u00a0but when it comes to filtering down a 5000 line project plan to activities in a specific timeframe, p6’s filters fall flat. \u00a0here’s the gotcha<\/strong>: any filter that uses a rolling date<\/a> or p6’s built-in date variables will not work when exporting p6 data to excel.<\/a><\/p>\n what variables are you talking about?<\/em><\/p>\n primavera p6 has the following 6 built-in date variables that can be used when building custom filters:<\/p>\n the workaround is pretty simple.<\/p>\n <\/p>\n although you’ll have to edit the dates in this filter over and over during the project, it’s much easier to filter activities in p6 than it is to try to filter them in excel.<\/p>\n oracle has yet to resolve this primavera p6 gotcha<\/a>, so make sure you drop them a line – “dear oracle….”\n
workaround for using p6 filters on export to excel<\/h2>\n
\n
\n
\n
\n<\/a>
\n<\/span>
\n