there are 2 point feature class(gridstation,substation) and 1 polyline featureclass(feader) ,due to some reasons it is not allowed to create geometric network, therfore i m using custom quries to generate diagram template from standard builder, gridstation and substation is appearing correctly with geometry attribute but feeder polyline is not . can u suggest me for configuring polyline feature class it has attribute source(gridstationid) and sink(substationid) as attribute field in feature class
First, I would recommend you try to figure out what the issue is with creating a geometric network as that will make it far easier to work with Schematics.
That said, to use custom query for this case it depends on everything going on so far. It sounds like you are actually trying to use 'mixed mode' where you have the point feature classes coming from the user making a selection on the map, but you want to run a query to get the links. Is that correct, or is everything custom query? This is a key thing to understand.
If you are having the user manually select the point features, then the identifier that schematics uses is a combination of classid-objectid-subid. You will see that value in the SCHEMTICTID column of the schematic feature class. So then for the link schematic feature class when doing custom query, you must specify 2 attributes in configuration for OriginNode and ExtremityNode. So these tell the link which 2 SCHEMATICTID records they connect with. Again, if those are coming from standard feature selection and not custom query, then you need to use a function attribute etc... in configuration to append the classid and subid to your girdstationid and substationid values so they match what the nodes have as a SCHEMATICTID.
Now, if everything is custom query (nodes and links), then it depends on what you specify as the UniqueIdentifier for the nodes. You still need the OriginNode and ExtremityNode configured and they need to match how you configure the unique identifier of the nodes.
There is a video available for Configuring Custom Queries on the resource center as well as lots of information in the help files. Custom Queries are definitely an 'Advance' configuration and again I would recommend figuring out how to fix your geometric network issues and only use custom query as a last resort. http://resources.arcgis.com/en/communities/schematics/01n600000012000000.htm
First, I would recommend you try to figure out what the issue is with creating a geometric network as that will make it far easier to work with Schematics.
That said, to use custom query for this case it depends on everything going on so far. It sounds like you are actually trying to use 'mixed mode' where you have the point feature classes coming from the user making a selection on the map, but you want to run a query to get the links. Is that correct, or is everything custom query? This is a key thing to understand.
If you are having the user manually select the point features, then the identifier that schematics uses is a combination of classid-objectid-subid. You will see that value in the SCHEMTICTID column of the schematic feature class. So then for the link schematic feature class when doing custom query, you must specify 2 attributes in configuration for OriginNode and ExtremityNode. So these tell the link which 2 SCHEMATICTID records they connect with. Again, if those are coming from standard feature selection and not custom query, then you need to use a function attribute etc... in configuration to append the classid and subid to your girdstationid and substationid values so they match what the nodes have as a SCHEMATICTID.
Now, if everything is custom query (nodes and links), then it depends on what you specify as the UniqueIdentifier for the nodes. You still need the OriginNode and ExtremityNode configured and they need to match how you configure the unique identifier of the nodes.
There is a video available for Configuring Custom Queries on the resource center as well as lots of information in the help files. Custom Queries are definitely an 'Advance' configuration and again I would recommend figuring out how to fix your geometric network issues and only use custom query as a last resort. http://resources.arcgis.com/en/communities/schematics/01n600000012000000.htm
