Standalone Rowset. Check if a Directory Exists. Think Time Functions. Export PeopleCode to File. Process Run Validation. Creating Cookies. Required Fields Cue. Showing and Hiding a Grid. Creating an Unique File Name.
The at Meta Operator. Dynamic From SQL. Open New Window PeopleCode. Creating Excel Files. We will look at how to do that in a later section. When you use a Container Rowset. In the example above there were two items in the XML that we mentioned that were important when syncing data. Those were of no use in the example where we were exporting data to a 3rd party system when the system asks for it. In that example above those attributes could cause some confusion.
You could probably remove them with an XSLT transform which we will cover in a later section. We will also see in in the Container Rowset section that these are stripped away. Where these attributes become useful are when we need to sync transactional changes between PeopleSoft systems. In these cases, we need to push incremental changes from one system to another. If a person deletes a row in a component, the subscribing system needs to have some sort of metadata of exactly what changed so it can mimic that change.
That is where these attributes come in. When you have a Rowset Message that is the exact same structure as a data entry component, the publication of changes becomes trivial. The PeopleTools framework handles all the setting of the metadata attributes in the message. The subscribing system can inspect the metadata and take appropriate actions. In the SavePostChange logic you might see something similar to this which would publish the changed data. To perform the copy, it uses like-named records for matching, unless specified.
In case if we had NOT created both the above rowsets from the same record, we would have mentioned the complete record names in the fill method as shown below. We have seen a standalone rowset being created usign a single record. However, we can also create one using another rowset. This would be handy to setup parent-child relations. This is how this can be achieved. Standalone rowsets are meant to be directly retrieved or populated from database at that point of time.
And hence CreateRowset method contradicts with the GetRowset method, which in fact refers to the component buffer data. I am using the code as above to pull data from a table and then populate a grid using a derived table and fields — my derfived table has exactly the same fields that my data table has — I am getting the correct number of records returned in my grid, but the field content is blank — the data does not show up?
Any suggestions would be greatly apprecaited. Your email address will not be published. Google Plus. So what are Standalone Rowsets?
0コメント