![]() ![]() ![]() ![]() Resource Codes and their dictionaries may be left as is, given a new ID and/or name or removed. Resources can also be given a new ID and/or name. Once a definition is saved, you can choose to remove any additional codes or dictionary values in subsequent MSP XMLs if they are not defined in the saved definition. Once the parent is created in P6, you may select it from the drop down in the Resource Remapping module. This allows you to isolate the imported resources to one parent upon import. The resources in an MSP XML can be imported under a pre-defined parent in your P6 database. Additional UDFs in subsequent MSP XMLs can be removed if they are not defined in the saved definition. UDFs may be left as is, renamed, or removed. All MSP Activity Codes are at the project level, so there is no need to roll down Global Activity Codes to the project level. You can set up the pattern you are looking for and P6-Scrubber will validate it when scrubbing your MSP XML.Īctivity Codes and their dictionaries may be left as is, given a new ID and/or name or removed. P6-Scrubber allows you to check adherence to ID and Naming conventions prior to import. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |