An issue that occured when using a cost start destination placeholder (e.g., coststartdestination.p15_name) when there was a cost without a start destination in the section that resulted in the costs name appearing has been resolved.  This issue only impacted Planner 2.0 itineraries.