Peoplesoft Queries Solutions

Converting User Filenames If a user attaches a file through the browser dialog box generated by the AddAttachment function, the filename may be converted before that filename is returned to the AddAttachment call for storage. For example, the file My Resume.doc is returned through the AddAttachment parameter as My_Resume.doc, with the space changed to an underscore. No comparable mapping occurs for user filenames with the PutAttachment function, which requires the user filename as an input parameter rather than an output parameter that is returned to the user. Instead, before storing the ATTACHUSERFILE value, you should invoke code similar to this: &ATTACHUSERFILE = Substitute(&ATTACHUSERFILE, " ", "_"); &ATTACHUSERFILE = Substitute(&ATTACHUSERFILE, ";", "_"); &ATTACHUSERFILE = Substitute(&ATTACHUSERFILE, "+", "_");

If your data is hierarchical in nature, or based on existing PeopleSoft records or pages, you want to use a File Layout definition for reading and writing your data, rather than doing it line by line (or field by field.) For example, suppose you wanted to write all the information from a record to a file. You can use the WriteRecord method to write all the data from the record, instead of having to loop through every field, find the value, and write it to the file. In addition, you could write all the information from a transaction (or several transactions) from a page to a file. Each transaction can be considered a  rowset . A rowset can contain more than one record and is generally composed in a hierarchical structure. You could create a File Layout definition that has the same structure as the page (or component), and use the WriteRowset method. If you have a file that contains data in the correct format, you can use the ReadRowset method to read the data from the file to the pa...