26/جمادى الأولى/1433 09:22 م
We recently migrated from PS2003 to PS2010 and the there are a few lookup tables for custom enterprise fields that will not populate the dropdown list in the project plan for their respective fields; they basically come up blank when selected. There are also many that translated fine and work correctly.
When I go to the view with the custom fields to make the selection from the lookup table there are no choices but if I type in correctly any of the choices that are in the lookup table directly into the field, they remain in the field. If I type incorrectly or something that is not in the list then the field remains blank.
This happens in the migrated PS2003 projects and also in any new projects I create in PS2010. We have experienced much Reporting Database Refresh errors and I'm starting to think this may be one of the issues because of these blank fields not being populated correctly. We have Rebuilt the Reporting Database many times per procedures found here in the forum and at the present we have not received any more errors in the last few days.
Can anyone tell me if this could be the problem with the Database errors and how I can fix my custom field lookups?
- Can I just delete and rebuild the troubled lookup tables?
- If so how does that effect any plans that reference these tables?
27/جمادى الأولى/1433 06:23 ص
Have you tried just opening those lookup tables in PWA (Server Settings > Enterprise Custom Fields) then saving each table again. Do any of these tables error when saving? After saving successfully do the values then appear in Project? If you look at the project details in PWA, do the values populate there?
27/جمادى الأولى/1433 02:28 م
I have gone in and re-saved the tables without any errors but got the same results. These fields do not show in PWA Project Details because they are Task and Resource specific not Project specific. Like I mentioned previously there are other custom tables in this same category (i.e. Task and Resource specific) that do function properly. I check to make sure they were setup the same in the Enterprise Custom Fields area so it's not obvious where the problem lies.
Any other thoughts?
27/جمادى الأولى/1433 04:31 م
27/جمادى الأولى/1433 04:55 م
I narrowed this down a bit.
In PWA the custom fields that appear to be working are Task fields and the ones that don't work are Resource fields.
When I bring up the project in Project Pro it acts as I have explained above; the Task field lookup list appears but the Resource field lookup does not appear but you can key in the appropriate choice and Publish the project.
In PWA edit mode the Task field lookup is active and appears and shows up the value when selected but the Resource field is non-active and even though the field has a keyed in value that shows up in Project Pro it does not appear in PWA. It's just blank and non-active.
28/جمادى الأولى/1433 04:48 مالمالك
Do yopu see the same behavior with any new resource fields created Forrest - or just with the migrated ones?
28/جمادى الأولى/1433 05:06 م
Brian I have not really created any new custom resource fields but I have built some new Project Plans on the new PS2010 system, which uses the same Global that migrated over. I get the same results.
- تم وضع علامة كإجابة بواسطة Forrest 10/جمادى الأولى/1434 06:03 م