Filter Conditions For Activity Codes Not Copying With File

As you are using Project Level Activity codes, the codes themselves are associated with the specific project they were created in, even if they are named the same. When you copy a project it effectively creates a new set of Project Level Activity Codes, but any filter you've created will continue to reference the original project activity codes (they match against internal Databsae ID's that you can't see)  However, as you haven't got the original project open, it cannot find these and therefore your filter conditions are blank. YOu have to redo your filter referencing the new project activity codes, even though they will appear to be the same.

You can check this behaviour by doing the following:

1) Open both proejcts, the original and the copied. Your filter will work, but will only filter activities from the original project

2) Open both projects and View the Activity Code list, you'll see they are grouped by project and both look the same.

Let me explain further:

Say you have ProjectX that contains an activity code called Zone, with code values of Zone A, Zone B & Zone C.

You create a filter that has a condtion Zone = Zone A and it works fine in Project X

Now you copy the project to ProjectY

Project Y now contains a Copied set of Activity Codes called Zone, with values Zone A, Zone B, Zone C etc.

However your original filter refereneces the Zone Activity Code from ProjectX not ProjectY.

You could try converting the Codes from Activity Level to EPS level and then they can be used across multiple proejcts and you can then use the same filter across all the projects. These codes will only be visible to users who can view projects in that EPS node, so shouldn't cause problems at a global level.

Thanks Santosh.

That makes sense, although does seem like it's a function

I as a secondary thought, I was wondering if there was a way of editing it in notepad if I save the layout filter and export it?

beacuse you cretae these as project codes if ther were created as global codes then they would be there.

make the global ones unique start the name with an astericks *

Chris,

I've never been able to make sense of a PLF file structure so I'm not sure if it'd be possible or not. The issue you'll face is that the Project Code in one Project has an Internal ID, and the same Code in the second project will have a completely different Internal ID and you'll need to be able to identify this value when you modify the PLF file - which I suspect might be a tough one.

Making the Codes EPS level (or global) is your best option, but if this is not possible, then the struggle of recreating the filters each time you copy the project is real. Perhaps your workflow needs to be modfied?

By that I mean rather than taking a copy, and then working in the copy, why not take a copy as snapshot, then continue working in the original project, and if/when you need to revert back to the how it was, you then go back to the copy and rebuild your filters in there.