Extending Schema

I am trying to extend the schema in our AD environment for SCCM 2012. I am in the schema admins group but I get the following errors after trying to extend the schema:
<01-06-2014 12:25:13> Modifying Active Directory Schema - with SMS extensions.
<01-06-2014 12:25:13> DS Root:CN=Schema,CN=Configuration,DC=ch,DC=org
<01-06-2014 12:25:15> Defined attribute cn=MS-SMS-Site-Code.
<01-06-2014 12:25:15> Defined attribute cn=mS-SMS-Assignment-Site-Code.
<01-06-2014 12:25:16> Defined attribute cn=MS-SMS-Site-Boundaries.
<01-06-2014 12:25:17> Defined attribute cn=MS-SMS-Roaming-Boundaries.
<01-06-2014 12:25:17> Defined attribute cn=MS-SMS-Default-MP.
<01-06-2014 12:25:18> Defined attribute cn=mS-SMS-Device-Management-Point.
<01-06-2014 12:25:19> Defined attribute cn=MS-SMS-MP-Name.
<01-06-2014 12:25:19> Defined attribute cn=MS-SMS-MP-Address.
<01-06-2014 12:25:20> Defined attribute cn=mS-SMS-Health-State.
<01-06-2014 12:25:21> Defined attribute cn=mS-SMS-Source-Forest.
<01-06-2014 12:25:21> Defined attribute cn=MS-SMS-Ranged-IP-Low.
<01-06-2014 12:25:22> Defined attribute cn=MS-SMS-Ranged-IP-High.
<01-06-2014 12:25:22> Defined attribute cn=mS-SMS-Version.
<01-06-2014 12:25:23> Defined attribute cn=mS-SMS-Capabilities.
<01-06-2014 12:25:23> Failed to create class cn=MS-SMS-Management-Point. Error code = 8202.
<01-06-2014 12:25:23> Failed to create class cn=MS-SMS-Server-Locator-Point. Error code = 8202.
<01-06-2014 12:25:23> Failed to create class cn=MS-SMS-Site. Error code = 8202.
<01-06-2014 12:25:23> Failed to create class cn=MS-SMS-Roaming-Boundary-Range. Error code = 8202.
<01-06-2014 12:25:23> Failed to extend the Active Directory schema, please find details in "C:\ExtADSch.log".
Im new at this and failed to backup the schema before executing this. Im trying to find out what the problem is. Does anyone know if this will cause huge issues since I did not back up the old schema? We are on Windows 2008 R2. If
I try to extend the schema again, will this cause issues as well?

Just to be clear you can run the command to extend the schema from any domain computer. You do not have to run it on the Schema Master. Also, as stated above, the account you are using must be a member of the Schema Admins.
Please don't take your Schema Master offline. Ensure that all DCs are online and operational and that replication is working successfully.
I have only seen this error once. In that situation there were issues with replication. When these issues were solved I was able to extend the schema.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson
This is all redundant information to the OP. It has been established that any machine on the domain that can reach the Schema Master DC can be used. The OP already stated in the original message that the account used is part of Schema Admins group.
And it is ENTIRELY possible to take the Schema Master offline and, as a matter of fact, MS even takes this approach in their TechNet article:
"If the schema extension procedure was unsuccessful, restore the schema master's previous system state from the backup created in step 1. This will reverse the schema extension actions before reconnecting the schema master domain controller to the network."
- Source
Not to mention these articles state it is possible and recommended as well.
Link1
Link2
Dustin Estes - MCP | www.dustinestes.com

Similar Messages

Extended Schema

Hello,
I am trying to extend my Active Directory schema in order to store my managed preferences in AD.
I am following this white paper : http://images.apple.com/business/solutions/it/docs/Modifyingthe_Active_DirectorySchema.pdf
I am unable to manage groups or computer lists. I cannot create a new computer list as I receive an error when attempting to do so. I have attempted to completely remove all of the extended schema changes, re-compare an OD master against the AD PDC, recreate the schema changes LDF, and re-apply the changes to no avail.
I do see the following in the debug logs:
2010-10-15 14:09:41 EDT - T[0xB0081000] - Active Directory: Using existing connection for testdomain.com - test.testdomain.com. user [email protected] cache MEMORY:YVKESUz
2010-10-15 14:09:41 EDT - T[0xB0081000] - Active Directory: Attempting to Create Record Type dsRecTypeStandard:ComputerLists Name Untitled_1
2010-10-15 14:09:41 EDT - T[0xB0081000] - Active Directory: Add record CN=Untitled_1,CN=Mac OS X,DC=testdomain,DC=com with FAILED - LDAP Error 19
Any help would be greatly appreciated.

To clarify: the objectClassCategory for apple-computer, apple-group, and apple-user should be 3; all the other classes should be imported with objectClassCategory set to 1. Nothing should have an objectClassCategory of 0.
I finally got a chance to test what happens if the apple-computer-list class is added to AD with objectClassCategory: 0, and the results match what you described. When I tried creating a computer list in Workgroup Manager, WGM popped up a dialog with the error "Not authorized. This action failed because you are not authorized to perform the operation.", and the DS debug log had this:
2011-01-22 18:19:57 PST - T\[0xB030B000\] - Client: Workgroup Manage, PID: 63007, API: dsCreateRecord(), Active Directory Used : DAC : Node Ref = 33576284 : Rec Type = dsRecTypeStandard:ComputerLists : Rec Name = Untitled_1
2011-01-22 18:19:57 PST - T\[0xB030B000\] - Active Directory: Using existing connection for example.com - windows-server.example.com. user [email protected] cache MEMORY:wHgljeI
2011-01-22 18:19:57 PST - T\[0xB030B000\] - Active Directory: Add record CN=Untitled_1,CN=Mac OS X,DC=example,DC=com with FAILED - LDAP Error 19
2011-01-22 18:19:57 PST - T\[0xB030B000\] - Client: Workgroup Manage, PID: 63007, API: dsCreateRecord(), Active Directory Used : DAR : Node Ref = 33576284 : Record Ref = 0 : Result code = -14120
2011-01-22 18:19:57 PST - T\[0xB030B000\] - Plug-in call "dsCreateRecord()" failed with error = -14120.
2011-01-22 18:19:57 PST - T\[0xB030B000\] - Port: 27927 Call: dsCreateRecord() == -14120
so having the zero objectClassCategory would account for the problem. Unfortunately, I don't know of any way to change the objectClassCategory once it's set. I hope this happened in a test environment, so you can fix it (set objectClassCategory to 1 for all but the apple-user, apple-group, and apple-computer) before rolling it out to live.
If this did make it to the live domain, there's a workaround: use AD tools (e.g. ADSI Edit) to create apple-computer objects inside the CN=Mac OS X container, then use WorkGroup manager to set them up.
BTW, there's a newer version of the Apple instructions at [http://images.apple.com/business/solutions/it/docs/L407117B-USMod_AD_Schema_Support_MacsWP-4.pdf], for Snow Leopard (the one you linked was based on Leopard). The changes aren't terribly important. They removed a bunch of stuff that Snow doesn't use, and added the apple-hwuuid attribute to apple-computer. But the stuff that was removed was hardly ever used under Leopard, and apple-hwuuid isn't actually needed for Snow Leopard, so in fact either set of instructions should work fine with either version of Mac OS X.

EPPM Extended schema functional description

Hi,
I have installed EPPM 8.3 using sql server database in a windows 2008 server.
In the documentation it says opening the PXReporting_83.dmd file I can find a functional description of a view in "Coments from RDBMS" property but there are no comments in any view in the model.
Is there any other place where I can found an explanation of every extended schema view ?
Thanks,

Here are the services you need to start:
Project Arbiter service
Publish Project service
Publish Enterprise Data
Publish Enterprise Summaries
Publish Resource Management
Publish Security
More info on the above is here: http://docs.oracle.com/cd/E20686_01/English/Technical_Documentation/Reporting_Database/P6%20Extended%20Schema%20White%20Paper.pdf
Information on the tables is in a thread I started (and answered) here: R8.2 Extended Schema Tables Question

Extending Schema for SCCM 2012 R2

I have looked everywhere for this information, but it's not listed in the LDF file nor is it notated on the MS documentation.
When extending the schema using extadsch.exe from the media for SCCM 2012 R2, does it touch the schema version or does it only add the classes required? Is there a difference in versions of extadsch.exe 5.0 and the exadsch.exe in the SCCM 2007 media?

Active Directory schema extensions for Configmgr 2012 are similar to the Active Directory schema extensions for Configmgr 2007.
If the schema was already extended for Configmgr 2007, you dont need to extend schema again for Configmgr 2012.
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

AD OD Extended Schema Computer Groups

Mac OS 10.6.5
Server 2003
AD-OD w/ Extended Schema
Kerberos
Hello,
So far I have a wonderfully working AD-OD setup with an extended schema. I have a few services running which require kerberos so I know that the foundation of the setup is solid. However, I am able to apply MCX settings to AD-users, user groups, and computers, but am unable to create computer groups with Workgroup Manager applied to AD. The error I get is:
This action failed because you are not authorized to perform the operation
The only way I have found to create computer groups is to switch WGM to the OD domain and add the AD computer objects to an OD managed computer group. I hope that makes sense...
The only information I've been able to find on the intertubes is this:
Did you create the Mac OS X container at the root of the domain?
AFAIK, all computer lists are automatically added to the Mac OS X container at the root of whatever domain you are pointed at. If that container does not exist, or you don't have the appropriate privs, you won't be able to create the computer lists.
If you are in a multi-domain environment and authenticate to "All Domains", WGM will attempt to create the computer list in the Mac OS X container located in your forest root domain.
At least thats been my experience. I can also add the WGM against AD has always been buggy for me. Random weird permissions errors don't always accurately reflect the outcome of an operation.
In the case of computer lists, I sometimes need to type * into the search box to find the lists I created, after I was told they weren't created
http://www.afp548.com/forum/viewtopic.php?showtopic=23022
I'm unsure of any container that Mac OS created at the root of the AD domain. I certainly don't see one listed in the AD Users and Computers GUI and wasn't aware that the extended schema was suppose to create one. The above quote was pulled from a 10.5.x thread so it may be outdated information.
Thanks for any and all suggestions!
Nick.

bumpskies

8.2 EPPM which process updates the extended schema?

Hello which process updates the 8.2 EPPM extended schema and is it possible to invoke from sqlplus command line?
Is there any doc. that shows which extended schema fields map to the main schema, are there any calculations being done or is it a straight copy?

Here are the services you need to start:
Project Arbiter service
Publish Project service
Publish Enterprise Data
Publish Enterprise Summaries
Publish Resource Management
Publish Security
More info on the above is here: http://docs.oracle.com/cd/E20686_01/English/Technical_Documentation/Reporting_Database/P6%20Extended%20Schema%20White%20Paper.pdf
Information on the tables is in a thread I started (and answered) here: R8.2 Extended Schema Tables Question

DSGW customisation. Has anyone else had problems getting Directory Express to allow users to edit extended schema attributes?

I can get the form to display extended schema but when editting the data it just returns errors.

Yes, the documentation is lacking in instructions on how to customise Directory Express. The Gateway Customisation Guide has instructions on how to do this in Chapter 5 under the section entitled Extending Object Classes.
I suggest you follow these first to set up your extended attributes for the DSGW.
The go into your Directory Express folder which is under dsgw/pbconfig and make a backup of the following file:
display-orgperson
then replace that file with the one you created when customising DSGW - display-airiusperson or whatever you called it.
When you next attempt to edit the person details in Directory Express, you will see that the form is the same as the one in DSGW. Maybe you can edit this to look like Express.
Good luck

R8.2 Extended Schema Tables Question

Can someone explain the difference between the extended schema’s tables with the same name, but different suffixies? For example: NAME, NAME_FULL, NAME_S and NAME_U. They seemingly have the same columns and data (rows).

I took some time today to look at the selects of the views. Here are some of my initial findings:
NAME - The select on the production tables, lots of column aliases to make the naming more intuitive. Filters out deleted sessions. The ETL, if you will.
NAME_FULL - This is simply a view of the above view with no new aliases or where statement. Basically SELECT * FROM NAME. This is presumably the view they want you to hit.
NAME_U - I assume the U stands for User. It basically does an INNER JOIN from the data (NAME view) you need to the PROJECTSECURITY, RESOURCESECURITY, GLOBALSECURITY, etc table(s) to limit the data. But not all of these views look at the security views/tables, therefore, you get the same data as the original view. No WHERE statement on these - the INNER JOIN effectively does it for you.
NAME_S (NOT MANY VIEWS INCL THIS ONE) - I assume the S stands for Secure Code, although one DBA mistakenly wrote out SECURITY instead of S on the pxrptuser.RESOURCE view. This view uses an inner joins to look at the object userIDs, secure code flags, etc.
This is what I needed for an immediate assignment, but I will be digging into these more and will edit this and/or post a better white paper on my web site.

Supressing the JAXB code for Extended Schemas using JWSDP

Hi,
Im trying to generate the JAXB code for the XML Schema using JWSDP using ANT build tool.
Q : My schema(eg., Schema01.xsd) extends other two schemas(Schema02.xsd, Schema03.xsd).Here using JWSDP package using ANT Build tool, i want to Generate the JAXB java classes only for Schema01.xsd not for other two schemas.
Can somebody help in this regard.
Note : By default using JWSDP, Ant build tool, in "Build.xml" it expects schema name(eg. Schema01.xsd"). when i generate the java code, it generates code for the Schema and as well as its all exetended schemas.
Q : how can supress generating the java code for the extended schemas.
Regards
Madhu

Hi, no I didn't notice this, tried it now and got
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><metadata xmlns="http://musicbrainz.org/ns/mmd-1.0#"><artist-list offset="0" count="1"><artist type="Group" id="ccd4879c-5e88-4385-b131-bf65296bf245" ext:score="100" xmlns:ext="http://musicbrainz.org/ns/ext#"><name>Echo & The Bunnymen</name><sort-name>Echo & The Bunnymen</sort-name><life-span begin="1978"/></artist></artist-list></metadata>is this right, its different to what I was originally trying to get

Question on best practice to extend schema

We have a requirement to extend the directory schema. I wanted to know what is the standard practice adopted
1) Is it good practice to manually create an LDIF so that this can be run on every deployment machine at every stage?
2) Or should the schema be created through the console the first time and the LDIF file from this machine copied over to the schema directory of the target server ?
3) Should the custom schema be appended to the 99user.ldif file or is it better to keep it in a separate LDIF ?
Any info would be helpful.
Thanks
Mamta

I would say it's best to create your own schema file. Call it 60yourname.ldif and place it in the schema directory. This makes it easy to keep track of your schema in a change control system (e.g. CVS). The only problem with this is that schema replication will not work - you have to manually copy the file to every server instance.
If you create the schema through the console, schema replication will occur - schema replication only happens when schema is added over LDAP. The schema is written to the 99user.ldif file. If you choose this method, make sure you save a copy of the schema you create in your change control system so you won't lose it.

Error when trying to extend schema

Installing SCCM2012 R2 into my test domain. I've created the System Management object and given permissions. I ran the extadsch.exe file from the SMSSetup\Bin\x64 directory of the install media. The result was "Failed to extend the
Active Directory schema, please find details in "C:\ExtADSch.log".
Looking at the log I see:
<01-28-2014 07:51:56> Failed to create class cn=MS-SMS-Management-Point. Error code = 8202.
<01-28-2014 07:51:56> Failed to create class cn=MS-SMS-Server-Locator-Point. Error code = 8202.
<01-28-2014 07:51:56> Failed to create class cn=MS-SMS-Site. Error code = 8202.
<01-28-2014 07:51:56> Failed to create class cn=MS-SMS-Roaming-Boundary-Range. Error code = 8202.
<01-28-2014 07:51:56> Failed to extend the Active Directory schema, please find details in "C:\ExtADSch.log".
So, I looked up Error code 8202. The notes I see refer to:
replication issues
Account used to run the schema extension not a member of Schema Admins
The account is definitely a member of the Schema Admins group. I have 2 DCs in the test domain, the first server is 2008 R2, the second is 2012 R2. I ran repadmin /showrepl and got the following:
Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\WILDDC1
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 0a9eca25-db8f-4b24-a1e5-40e4e346263a
DSA invocationID: 0a9eca25-db8f-4b24-a1e5-40e4e346263a
==== INBOUND NEIGHBORS ======================================
DC=WILD,DC=XXX,DC=XX,DC=XXX
Default-First-Site-Name\WILDDC2 via RPC
DSA object GUID: ec3bd941-b372-4094-a15a-7e0c218a9a9c
Last attempt @ 2014-01-28 07:54:33 was successful.
CN=Configuration,DC=WILD,DC=XXX,DC=XX,DC=XXX
Default-First-Site-Name\WILDDC2 via RPC
DSA object GUID: ec3bd941-b372-4094-a15a-7e0c218a9a9c
Last attempt @ 2014-01-28 07:52:01 was delayed for a normal reason, result 8418 (0x20e2):
The replication operation failed because of a schema mismatch between the servers involved.
Last success @ 2014-01-28 06:52:01.
CN=Schema,CN=Configuration,DC=WILD,DC=xxx,DC=xx,DC=xxx
Default-First-Site-Name\WILDDC2 via RPC
DSA object GUID: ec3bd941-b372-4094-a15a-7e0c218a9a9c
Last attempt @ 2014-01-28 07:52:04 was successful.
DC=DomainDnsZones,DC=WILD,DC=xxx,DC=xx,DC=xxx
Default-First-Site-Name\WILDDC2 via RPC
DSA object GUID: ec3bd941-b372-4094-a15a-7e0c218a9a9c
Last attempt @ 2014-01-28 07:52:01 was delayed for a normal reason, result 8418 (0x20e2):
The replication operation failed because of a schema mismatch between the servers involved.
Last success @ 2014-01-28 06:52:01.
DC=ForestDnsZones,DC=WILD,DC=xxx,DC=xx,DC=xxx
Default-First-Site-Name\WILDDC2 via RPC
DSA object GUID: ec3bd941-b372-4094-a15a-7e0c218a9a9c
Last attempt @ 2014-01-28 07:52:01 was delayed for a normal reason, result 8418 (0x20e2):
The replication operation failed because of a schema mismatch between the servers involved.
Last success @ 2014-01-28 06:52:01.
So, I do have a couple of replication issues. Any idea how to resolve them?

Long shot: did you try extending the schema using the ldifde util and the ConfigMgr_ad_schema.ldf ?
In any case it'll give you more details and probably point you into the right direction for troubleshooting.
Update: procedure is documented here:
http://technet.microsoft.com/en-us/library/bb632388.aspx (2007 article but the process is identical)

ADSI and extended schema

I am using iPlanet Directory Server 5.1SP2 on Solaris 8 in a replicated environment (Multi Master with iDar for load balancing and fail over).
I've created an object class by extending the inetOrgPerson class and included some new attributes.
Then, I use ADSI functions to get informations related to users.
All it's ok until I update the objectClass I created with a new attribute and added this attribute to user entries.
Any search performed on entries asking the new attribute returns an error similar to this one for a not existing attribute.
It seems that ADSI calls does not see the new attribute in the schema.
Note that any LDAP query (ldapsearch, I mean) works fine.
All the extension operations of the schema have been made correctly (by console and replicated, not directly in 99users.ldif).
There can be any problem of caching of the schema ?
Is it a caching on DS side or ADSI side ?
How can I force to get a refreshed view of the schema ?
Thanks for any info.
Marina

I am using iPlanet Directory Server 5.1SP2 on Solaris 8 in a replicated environment (Multi Master with iDar for load balancing and fail over).
I've created an object class by extending the inetOrgPerson class and included some new attributes.
Then, I use ADSI functions to get informations related to users.
All it's ok until I update the objectClass I created with a new attribute and added this attribute to user entries.
Any search performed on entries asking the new attribute returns an error similar to this one for a not existing attribute.
It seems that ADSI calls does not see the new attribute in the schema.
Note that any LDAP query (ldapsearch, I mean) works fine.
All the extension operations of the schema have been made correctly (by console and replicated, not directly in 99users.ldif).
There can be any problem of caching of the schema ?
Is it a caching on DS side or ADSI side ?
How can I force to get a refreshed view of the schema ?
Thanks for any info.
Marina

Problem extending schema

Hi,
we've installed NSM 3.1.1.1 on a Windows 2012 Standard with Active Directory and forest level 'Windows2012Forest'.
The account doing the schema update is both domain and schema admin.
NSM Admin says that the schema is not extended
When starting the installation it says:
- Current Forest level 5 is good
- all three ccs- attribute/class schema extensions do not exist
- one or more schema extensions need extending
When start the action, the following error messages appear:
Stack Trace: at System.DirectoryServices.ActiveDirectory,ActiveDir ectorySchemaProperty.Sae
at ADSchemaExtension.AttributeExtension.AddToSchema()
Exception adding attribute to schema: The object already exists

On 7/9/2014 7:46 AM, anitone wrote:
>
> Hi,
>
> we've installed NSM 3.1.1.1 on a Windows 2012 Standard with Active
> Directory and forest level 'Windows2012Forest'.
> The account doing the schema update is both domain and schema admin.
> NSM Admin says that the schema is not extended
>
> When starting the installation it says:
> - Current Forest level 5 is good
> - all three ccs- attribute/class schema extensions do not exist
> - one or more schema extensions need extending
>
> When start the action, the following error messages appear:
> Stack Trace: at
> System.DirectoryServices.ActiveDirectory,ActiveDir ectorySchemaProperty.Sae
> at ADSchemaExtension.AttributeExtension.AddToSchema()
> Exception adding attribute to schema: The object already exists
>
>
anitone,
Please send an email to [email protected] -- we have an updated
build of NSM we can send you which fixes this issue.
-- NFMS Support Team

Dynamically extending schema

I want to give the userof the application a facility to add more columns to any table in the database schema.
Typically, columns in the database schema will get populated from the entity bean fields. But we want to put the extra information for the fields the user creates dynamically in a XML doc and put the doc as a column in the Table.
The problem is as follows:
1. How do I put some fields of entity bean into XML file while others will end up as populating the appropriate Table in the database?
2. Similiar thing is expected while loading from database and XML file The SQL query has to read from the database Tables besides extracting the fields from XML file ( which is stored as a database column )

clarification:
1. we want to extend the database schema dynamically . Addition of new columns will be an example.
2. The end user would like to add some more fields from the UI.
3. The field names and values will end up in an XML file finally.
4. The XMLschema/dtd and XML file will be stored as a CLOB column in the database
I would like to understand how it can be achieved. For some reason we do not want to add a Table which can have new columns corresponding to the new fields entered by the user.
thanks

XMLBeans 2.0 - Problem with derived/extended schema elements

Hi,
I have a schema which takes a list of "Record" types. Each 'Record' is complex type of SenderDetails, Recipientdetails, shipdate, description and Ref elements. The main.xsd is as follows:
<xs:element name="records">
<xs:complexType>
<xs:sequence>
<xs:element name="record" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="SenderDetail" type="cmn:AddressType" />
<xs:element name="Shipdate" type="xs:string"/>
<xs:element name="RecipientDetail" type="cmn:AddressType" />
<xs:element name="Description" type="xs:string"/>
<xs:element name="Ref" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Now, the SenderDetail and the RecipientDetail may be of type 'Employee' or 'Department'. Employee and Department are both derived from 'AddressType' as shown.
<xs:complexType name="Department">
<xs:complexContent>
<xs:extension base="cmn:AddressType">
<xs:sequence>
<xs:element name="Name" type="xs:string" />
<xs:element name="keyvalues" type="cmn:Valuelist"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Employee">
<xs:complexContent>
<xs:extension base="cmn:AddressType">
<xs:sequence>
<xs:element name="Name" type="xs:string" />
<xs:element name="Title" type="xs:string" />
<xs:element name="Empid" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
After mapping the schema to java objects, here I am using the following code to check whether the 'SenderDetail' in the incoming xml is of type 'Employee' or 'Department'.
'records[]' is the array of records already extracted from incoming xml.
Here the output of "System.out.println( records.getSenderDetail() ); "
Output:
<xml-fragment xsi:type="o:Employee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:p="SomeX/Records"
xmlns:o="SomeX/Stakeholder"
xmlns:c="SomeX/CommonTypes">
<c:street1>456 Oak Lane</c:street1>
<c:street2>Second floor bld I</c:street2>
<c:city>xxx</c:city>
<c:state>xxx</c:state>
<c:country>US</c:country>
<c:zipcode>xxx</c:zipcode>
<c:phone>xxx</c:phone>
<c:comail>xxx</c:comail>
<o:Name>xxx</o:Name>
<o:Title>xxx</o:Title>
<o:Empid>xxx</o:Empid>
</xml-fragment>
Now I am expecting the output of the following code
AddressType p = records[i].getSenderDetail();
if (p instanceof Employee){
System.out.println("Sender is of type Employee");
}else if (p instanceof AddressType){
System.out.println("Sender is of type AddressType");
to be "Sender is of type Employee"
But I am getting "Sender is of type AddressType"
records[i].getSenderDetail().schemaType() on this record is giving me the base schema type "AddressType"
How can I get the derived schema type ? How can i know whether this is a Employee/Department type?
Thank You.

If your query1 is something like
SELECT ...
d.deptno,
FROM
...dept d
WHERE ...
and you want to do query2
SELECT ...
FROM ...
for all departments but then split the output on display by department.
I'd go with the suggestion from the other poster above:
Do your query1 as
SELECT ...Query1Fields,
Query2Fields
FROM Query1Tables, (put query2 here) q2
where q2.deptno = dept.deptno -- or whatever the conditions are
Or use
WITH q2 AS (put query2 here)
SELECT ...Query1Fields,
Query2Fields
FROM Query1Tables, q2
where q2.deptno = dept.deptno -- or whatever the conditions are
That second format should ensure that query2 is done as one whole unit.
Then in the data model drag and drop the query2fields outside the query1 group to form a new group below it. Then in the layout you have a repeating group based on the query1 group and within it a repeating group based on the new "query2" group.

Extending Schema

Similar Messages

Maybe you are looking for