Importing Project w/ Parent Milestones about milestones-pm

[pjkellyjr]

Just to clarify...I'm referring to using the "Import Template" XML method of transferring a Project (and related Milestones/Tasks) from one Org to another.

[ReidCarlberg]

yeah I don't know that the import feature includes the parents. When you say random what are you actually seeing? Its ome but not all parents? Or it's all parents with an ocassional error?

[pjkellyjr]

Yes, some but not all parents are importing via the "Import Template" XML
method.
I ran several tests and it appears to be importing the same set of Parent
Milestones..., but I'm not sure what it is about those Parent Milestones
that allows them to import successfully.
Thanks Reid,
Patrick

On Tue, Jan 24, 2012 at 7:43 AM, ReidCarlberg <
[email protected]

wrote:

yeah I don't know that the import feature includes the parents. When you
say random what are you actually seeing? Its ome but not all parents? Or
it's all parents with an ocassional error?

---

Reply to this email directly or view it on GitHub:

#44 (comment)

Patrick J Kelly Jr ▪ VP, Implementation ▪ TargetX
[email protected] ▪ 877.715.7474 x105 ▪ AIM: pjkellyjr

Happy Holidays from TargetX !
We're looking forward to another great year in 2012.

Visiting us often at www.facebook.com/targetx

[ReidCarlberg]

April 2012 steps 1) create a new test method what builds data with dependencies 2) this should have both dependent tasks and milestones 3) use the export process to create a string 4) import from that string to a new project 5) ensure those dependencies are imported correctly.

Here's the screenshot for a predecessor task: https://skitch.com/reidcarlberg/8umsh/task-6-task-picklist-configuration-salesforce.com-developer-edition

Here's how you set a predecessor milestone: https://skitch.com/reidcarlberg/8um3m/force-quit-applications

[pjkellyjr]

Thanks for the update.
Looking forward to the enhancements.
Patrick

On Tue, Mar 20, 2012 at 4:07 PM, ReidCarlberg <
[email protected]

wrote:

April 2012 steps 1) create a new test method what builds data with
dependencies 2) this should have both dependent tasks and milestones 3) use
the export process to create a string 4) import from that string to a new
project 5) ensure those dependencies are imported correctly.

---

Reply to this email directly or view it on GitHub:

#44 (comment)

Patrick J Kelly Jr ▪ VP, Implementation ▪ TargetX
[email protected] ▪ 877.715.7474 x105 ▪ AIM: pjkellyjr

Happy Holidays from TargetX !
We're looking forward to another great year in 2012.

Visiting us often at www.facebook.com/targetx

[eclf]

Hi, I'm very interested in these enhancements as well.
I've tried adding some things to the export/import functionalities that were important for the company, like Dates and Estimated Costs, and most importantly dependencies (Parent/Child, Predecessor/Successor) between Milestones & Tasks. The problem is that when importing it was attempting to link the new project with the Milestones/Tasks of the other project (the one to export to the xml as template, for example), and there are validation rules to prevent that because it's not supposed to.
In small projects I guess there would be no problem in importing and then setting the dependencies manually, but in big ones...
If anyone please finds a solution please, let me know.
Thkns

[ReidCarlberg]

Here's a new Lookup Filter that we need to have on the Milestone1_Milestone__c object. It restricts the values of the "Predecessor Milestone" field to Milestones with the same Project and Parent Milestone Values.

https://skitch.com/reidcarlberg/8irwq/milestone-custom-field-predecessor-milestone-salesforce.com-developer-edition