Some attributes are not writing to a custom object
The problem I am experiencing is that we have a policy that is creating a new object (using a custom class called OSUappointment). In the log file, we can see all of the attributes being created (using set destination commands). however, randomly, some attributes are not written to the new object.
For example, we have a userID : IDM801803765
An attribute on the userID (OSUflag-WorkdayAppt) is a blob looks similar to this (an XML blob, if you will):
<OSUjobcdJobTitle>Instructor - Practice</OSUjobcdJobTitle>
<OSUpstnWorkTitle>Instructor - Practice</OSUpstnWorkTitle>
<OSUdeptDescription>Nursing | College Administration</OSUdeptDescription>
<OSUlocBuilding>Newton Hall (0275)</OSUlocBuilding>
<SA>1585 Neil Ave</SA>
<OSUcampCountry>United States of America</OSUcampCountry>
A policy in the conversion driver, OSU-sub-ctp-ProcessAppointments, processes this blob. It takes each element of the blob and converts it into a set destination command, so that the document in the driver look like this:
This is just a slice of the entire document. All of the elements in the blob above will be in the document along with several other attributes (OSUidmID, OSUPSemplId, etc...). The file novelTicket.txt is a copy of the log file where the userID, IDM801803765, comes in with the flag OSUflag-WorkdayAppt changing.
In this case, the object being created is of objectClass 'OSUappointment' and the name of the object is 500016140-00086267-Appt. the object itself is a direct create, while the rest of the attributes are created as a "set Destination Attribute Value" (do-set-dest-attr-value). From what I can tell of the log file, all of the attribute go through and are added to the new object... but, randomly, some attribute never seem to make it to the object.
Typically, the follow attribute never make it to the new object (500016140-00086267-Appt)
There are others, but I am going from memory, so I cannot tell for sure what the other are (the above are for sure, though).
We have looked at other drivers that have one or more of the 4 attribute and never make it to see of any of these drives are deleting the attributes, but nothing is deleting these attributes. AND, like I mentioned above, the attributes are random on whether these are on the new object or not. Mostly, these are on the object, but, again, it seems to be random.
Has anyone experienced this before? Does anyone have any ideas what could be causing this? The attached file is a partial log containing the log where one object does not get all of the attributes in the document.
I believe, that you use OSUappointment AUX class
In many cases engine "add" missing AUX class on the fly, but I also see the situation, that it doesn't happen (for unknown reason).
I prefer to add required AUX class names to the objectClass attribute during object creation and didn't take a chance...
Could you check, if you have all required object classes in the objects, that you miss attributes?
You can add a filter that listen on the attributes you are missing and see them created, modified and deleted. Maybe even run this driver alone and see that the attributes are available after your creation process.
These "some" attributes related to OSUappointment class.
Is it AUX or Effective class?
When these attributes didn't survive, do you see proper AUX class in the ObjectClass attribute?
The only two classes that I see are (complete and non-complete objects):
- OSUappointment (Structural)
- Top (Structural)
The "some" attributes are in the OSUappointment class... some of those attributes are in other classes as well.