Servicio BAO, market_report - leyendas de campo extrañas

Question

<\/HEAD>Hola,<\/SPAN> Actualmente estoy trabajando con ESRI en mi aplicación y usando una cuenta de prueba.<\/SPAN> Hice una llamada REST y recibí una respuesta que contiene rutas S.XML y PDF.<\/SPAN> Estoy intentando analizar los datos S.XML para el informe de mercado.<\/SPAN> El informe de perfil de mercado contiene muchos datos con campos de descripción muy extraños, por ejemplo:<\/SPAN> *************************<\/SPAN> <\/SPAN> <\/SPAN> <\/SPAN> <\/SPAN> <\/SPAN> <\/SPAN> <\/SPAN> <\/SPAN> ***********************<\/SPAN> Todos los campos en el PDF contienen leyendas legibles.<\/SPAN> ¿Alguien tiene idea de por qué obtengo estas leyendas SCRIPT*** y nombres de campo??<\/SPAN> ¿Cómo puedo mapear todos estos valores con nombres razonables contenidos en el PDF?<\/SPAN> Supongo que es por mi cuenta de prueba. ¿Qué opinas?<\/SPAN> Gracias<\/SPAN><\/BODY><\/HTML>

esritony · Answer

Hi mickogricko, Thank you for your patience. The "S.XML" (simplified XML)/XML-based output "report" formats are excellent options for consuming the data and *calculations* which are displayed/formatted in the PDF versions of the report. This way you can easily consume the information and leverage it in your systems, workflows, and applications. I completely empathize with you regarding your experience with the current "caption" attributes of many of the XML records returned with the S.XML and XML versions of the reports. Ideally, we should be providing "captions" that more closely represent the field descriptions in the PDF versions of the reports. This is a challenge since the fields are often nested in sub-fields and sub-headings, etc. We are assigning resources to address this challenge in our future releases. In the mean time, what you can do is map/associate the XML record (of the S.XML or XML versions of the report output) with a caption that you want to represent in your client application. You can generate both the PDF and S.XML/XML versions of the report simultaneously during application designtime and map the "name" attribute with the data or *calculated* field that interests you or is important to your system and/or stakeholders. We sincerely appreciate your frank feedback. This is extremely valuable for us. If we did not capture this feature request appropriately, please feel free to contact us through the bao_support@esri.com email and reference your Forum discussion with Tony. We are very interested in making sure the API meets your needs (because it will likely help our other customers' needs as well). Thank You! Tony EXAMPLE: (1). REST request to generate Esri Business Analyst Market Profile Report on the 92373 ZIP code in PDF and S.XML versions simultaneously: http://baoapi.esri.com/rest/report/SummaryReports?Boundaries={"StdLayer":{"ID":"US.ZIP5","geographyIDs":["92373"]}}&ReportOptions=[{"TemplateName":"market_profile","ReportFormat":"PDF"},{"TemplateName":"market_profile","ReportFormat":"S.XML"}]&f=json&TaskOutputType=GetReport&Token=iraIdzBCKv1fPYO5EU4oljNg3JvL1bz4d46yNBpBQ2SrHRp7uHA1UHiYuq2sFW9c& (2). View both of the report formats; identify the fields that are important to you in the PDF version of the report; and map this selected item in the PDF version of the report with the corresponding XML ReportItem record's "name" attribute: Market Profile Report (PDF ) ---------snip----------- 2010 Housing Units (14,577) [name="TOTHU_CY" in S.XML below] Housing Units Summary -> 2010 Housing Units -> Owner Occupied Housing Units (49.5%) ] [name="SCRIPT_C_2" in S.XML below] Housing Units Summary -> 2010 Housing Units -> Renter Occupied Housing Units (45.1%) [name="SCRIPT_C_3" in S.XML below] Housing Units Summary -> 2010 Housing Units -> Vacant Housing Units (5.4%) [name="SCRIPT_C_4" in S.XML below] ---------snip----------- Market Profile Report (S.XML ) ---------snip----------- ---------snip-----------

esritony · Answer

Hi mickogricko,

I am sorry that the caption attribute values in the XML records are not entirely helpful in associating the PDF fields with the XML document.  We are currently having our engineers look into the issue.  I will try to respond by this evening or tomorrow at the latest after I get more information for you.  If you have any further details to provide us, please send it to bao_support@esri.com or feel free to log you issue with SDK Support at 888-377-4575.

Thank you very much for your extreme patience and understanding.

-Tony

MilicaBogicevic · Answer

I still have problem!!!

Can someone help me?

Thanks!