Inserting XMLP File Definitions into Projects March 12, 2008
Posted by Duncan in PeopleTools.trackback
There have been a couple of occasions where the file definition (the template file behind the XMLP Report Definition) has become out of sync with what is in the project.
This may be because the file was inserted into the Project, and then a subsequent change made to the template and uploaded into PeopleSoft. In this case, the updated Report Definition and Template Definition would be migrated, but the new file wouldn’t be in the project so it wouldn’t be taken across. Unfortunately this leads to a really rather nasty message in the PIA.
The solution is clearly to re-add the File Definition in to he project, but it’s not always straightforward. You can select it as a related definition when you insert the template, but sometimes this inserts the old (overwritten file). To be sure you have the file inserted, you have to add it manually. The only issue is the insert file definition dialogue box is not helpful.
The search field only allows you to search on the long alphanumeric string, not the actual filename so you end up scrolling through the full list attempting to spot the file you’re after. As more reports get developed, the list will get longer.
The alternative is to use some SQL:
SELECT FILEID
FROM PSFILEDEFN
WHERE USERFILENAME = '<filename>'
This gives you the File ID, which is what the dialogue box searches on, enabling you to find your template file a lot quicker.
Comments
Sorry comments are closed for this entry
The PeopleSoft Tipster Blog 
I am wondering when we upload a template file in the XML Publisher online where it is storing?
How is the uniqueness of file id maintained across different instances? For e.g. if we copy a file id from DEV to QA and also allow to add it manually in QA system, will it cause any conflict?
@Guest, if you want to know the table behind any PeopleSoft activity, the best thing to do is trace it. I suspect the table may well be PSFILE_ATTDET though.
@Ketan, I assume the uniqueness is maintained (but not ensured) by use of the long alphanumeric string. The chances of a match are slim. Should you allow your developers to modify templates files or project definitions directly in QA though? I’d have thought they should be correcting the project in DEV and re-migrating …
I have a great idea! We need to have a site/blog that we can upload sample *.rtf templates to and do some sort of sharing of templates. Do you know if something like this already exists on the Oracle site? I am sure there are a bunch of templates that can be shared accross the board.
There is a problem that occurs when inserting XMLP File Definitions by inserting an XMLP Report Defn and using the Related Definitions to insert the file definitions.
When you do this it seems to insert the files OK, but if you were to do a compare of your project at this point in time, the file definitions it inserted automatically show up as Absent in both the Source and Target.
What you then have to do is insert the file definition manually, not by using the Related Definition method and inserting files with the same names that were inserted originally.
You will now see under the Upgrade tab that the files you added manually actually appear twice in XMLP File Defn.
This information is really helpful..
What you then have to do is insert the file definition manually, not by using the Related Definition method and inserting files with the same names that were inserted originally.
You will now see under the Upgrade tab that the files you added manually actually appear twice in XMLP File Defn.
Above info is very Useful. Thanks a bunch