nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

e-search error (RPC Fault FaultString="")

PATRICIACOSMOPOULOS

Hi again,

My esearch stopped working after some changes I made mostly to the service/mxd. I have attached the error I am getting and the esearch.xml code as text. Even though I backtracked a couple of steps the error seems to persist. The problem started when I tried to join (one to one) two shapefiles with common ID field. Identify seemed to work well with this but then all symbols disappeared from the map view and search stopped working.

Can somebody point me in the right dirrection? Would it be better the delete this widget and start with a new download?

Thanks
Patricia

eSearchWidget.txt.zip

esearch error.jpg

Find more posts tagged with

Accepted answers

All comments

PATRICIACOSMOPOULOS

It worked! Thanks for your help! Is it possible that the text labels do not show for a similar reason?

Patricia

Anonymous User

Original User: CEAAGIS

Yes you are right I checked the other layers that do not have any joins and they do not show the database and table info. I will try and let you know.

patricia

rscheitlin

Patricia,

So your issue is that you need to use the WHOLE field name (as it is displayed in the REST service directory).

upper(CEAAGIS.CEAAGIS.CEAAPoints1.Titre) LIKE upper('%[value]%')

And also the whole field name when listing the fields as well.

Anonymous User

Original User: ad_giles@hotmail.com

Patricia,

I think where you have made the join has changed how the fields are accessed via the rest endpoint, you need to put the field name in as it appears in you rest endpoint which now includes the table name etc, I.e:

CEAAGIS.CEAAGIS.CEAAPoints1.OBJECTID

Regards

Anthony

PATRICIACOSMOPOULOS

Also forgot to mention I have joined one shapefile with another using a unique field.
Could this be part of the problem? I can see the extra fields in rest services:

CEAAGIS.CEAAGIS.CEAAPoints1.OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )
CEAAGIS.CEAAGIS.CEAAPoints1.Label ( type: esriFieldTypeString , alias: Label , length: 10 )
CEAAGIS.CEAAGIS.CEAAPoints1.Longitude ( type: esriFieldTypeDouble , alias: Longitude )
CEAAGIS.CEAAGIS.CEAAPoints1.Latitude ( type: esriFieldTypeDouble , alias: Latitude )
CEAAGIS.CEAAGIS.CEAAPoints1.Lien ( type: esriFieldTypeString , alias: Lien , length: 100 )
CEAAGIS.CEAAGIS.CEAAPoints1.Titre ( type: esriFieldTypeString , alias: Titre , length: 100 )
CEAAGIS.CEAAGIS.CEAAPoints1.�?tiquette ( type: esriFieldTypeString , alias: �?tiquette , length: 10 )
CEAAGIS.CEAAGIS.CEAAPoints1.Region_FR ( type: esriFieldTypeString , alias: Region_FR , length: 60 )
CEAAGIS.CEAAGIS.CEAAPoints1.Shape ( type: esriFieldTypeGeometry , alias: Shape )
CEAAGIS.CEAAGIS.CEAAPoints1.Project_Type_FR ( type: esriFieldTypeString , alias: Project_Type_FR , length: 50 )
CEAAGIS.CEAAGIS.Registry2012.projectID ( type: esriFieldTypeInteger , alias: projectID )
CEAAGIS.CEAAGIS.Registry2012.titleFR ( type: esriFieldTypeString , alias: titleFR , length: 256 )
CEAAGIS.CEAAGIS.Registry2012.postDate ( type: esriFieldTypeDate , alias: postDate , length: 36 )
CEAAGIS.CEAAGIS.Registry2012.RAsFR ( type: esriFieldTypeString , alias: RAsFR , length: 50 )
CEAAGIS.CEAAGIS.Registry2012.descFR ( type: esriFieldTypeString , alias: descFR , length: 150 )
CEAAGIS.CEAAGIS.Registry2012.proponentFR ( type: esriFieldTypeString , alias: proponentFR , length: 300 )
CEAAGIS.CEAAGIS.Registry2012.URL_f ( type: esriFieldTypeString , alias: URL_f , length: 100 )
CEAAGIS.CEAAGIS.Registry2012.typeFR ( type: esriFieldTypeString , alias: typeFR , length: 255 )
CEAAGIS.CEAAGIS.Registry2012.statusFR ( type: esriFieldTypeString , alias: statusFR , length: 254 )

Anonymous User

Original User: CEAAGIS

Hi Robert,

I have two apps one in English and the other in French so I have services in both languages. The services are using the same shapefiles but different fields depending on language. In both cases the error is the same. Previously the attachment had the code for french service. Checked the url and it gave me the correct layer and fields. So URL and code for the fields seems correct. I have attached a screen capture in case it helps.

Thanks,
Patricia

restservices.jpg

rscheitlin

Patricia,

Are you sure that this is a valid SQL?

upper(Titre) LIKE upper('%[value]%')

Check the spelling of all your field names:

            <fields all="false" >
                <field name="Titre" alias="Project Title" gridfield="true" />
                <field name="Project_Type_FR" alias="Project Type" gridfield="true" />    
                <field name="Status_FR" alias="Project Status" gridfield="true" />
                <field name="Region_FR" alias="Region" gridfield="true" />    
                <field name="Label" alias="Label" gridfield="true" />    
                <field name="Lien" alias="Link" gridfield="true" />    
                <field name="Latitude" alias="Latitude" gridfield="true" />    
                <field name="Longitude" alias="Longitude" gridfield="true" />            
            </fields>

Also check that your url is correct.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.