Planned For Not Getting Recognized on Import
![](http://jazz.net/_images/myphoto/60d9d3567e4772176551cc1aba8029ab.jpg)
I do a lot of data importing into RTC and have found that, when I include Planned For, its values don't seem to get registered properly. The values show up correctly if I do a query, but they don't actually should up in the plan display for the plan specified by the Planned For values. This is true even after I refresh the plan display. Instead, I have to bulk change the Planned For values, seemingly to the exact same values that are already there, before they show up. This makes the import more tedious and time-consuming than it should be. Any thoughts?
2 answers
![](http://jazz.net/_images/myphoto/60d9d3567e4772176551cc1aba8029ab.jpg)
I do a lot of data importing into RTC and have found that, when I include Planned For, its values don't seem to get registered properly. The values show up correctly if I do a query, but they don't actually should up in the plan display for the plan specified by the Planned For values. This is true even after I refresh the plan display. Instead, I have to bulk change the Planned For values, seemingly to the exact same values that are already there, before they show up. This makes the import more tedious and time-consuming than it should be. Any thoughts?
Are You using the name instead of the iteration id perhaps ?
![](http://jazz.net/_images/myphoto/60d9d3567e4772176551cc1aba8029ab.jpg)
I do a lot of data importing into RTC and have found that, when I include Planned For, its values don't seem to get registered properly. The values show up correctly if I do a query, but they don't actually should up in the plan display for the plan specified by the Planned For values. This is true even after I refresh the plan display. Instead, I have to bulk change the Planned For values, seemingly to the exact same values that are already there, before they show up. This makes the import more tedious and time-consuming than it should be. Any thoughts?
Are You using the name instead of the iteration id perhaps ?
Yes. The plan name and the iteration id are the same.