Latest Contributions by JasonNielsen

Hey Jason, I noticed that this is an issue with the Edit Widget where the <formfieldsorder> is not being honored. Having looked at it in more detail and to be consistent with other widgets, i think it would make sense that if the fields are being specified explicitly in a certain order in the config, then there is no need to specify <formfieldsorder> as it would be redundant. Here's the fix (if you are using the uncompiled version) for the EditWidget.mxml, replace the attributeInspector_showFeatureHandler() method with: private function attributeInspector_showFeatureHandler(event:AttributeInspectorEvent):void             {                 attachmentInspector.addEnabled = editor.attributeInspector.updateEnabled;                 attachmentInspector.deleteEnabled = editor.attributeInspector.deleteButtonVisible;                 const featureLayer:FeatureLayer = event.featureLayer;                 var settingsKey:String = featureLayer.name;                 if (featureLayer.name.indexOf("hiddenLayer_") != -1)                 {                     settingsKey = hiddenFeatureLayerToSettingsName[featureLayer];                     if (!settingsKey)                     {                         settingsKey = featureLayerToDynamicMapService[featureLayer].name +                             "/" + featureLayer.url.substring(featureLayer.url.lastIndexOf("/") + 1, featureLayer.url.length);                         hiddenFeatureLayerToSettingsName[featureLayer] = settingsKey;                     }                 }                 var settingsObject:Object = layerToSettings[settingsKey];                 if (settingsObject)                 {                     var outFields:Array = settingsObject.outFields as Array;                     if (outFields && outFields.length)                     {                         var attributeInspectorFieldInspectors:Array = [];                         var fieldInspector:FieldInspector;                         for each (var fieldObject:Object in outFields)                         {                               fieldInspector = new FieldInspector;                             fieldInspector.featureLayer = featureLayer;                             fieldInspector.visible = true;                             fieldInspector.fieldName = fieldObject.name;                             fieldInspector.label = fieldObject.alias;                             fieldInspector.toolTip = fieldObject.tooltip;                                                         attributeInspectorFieldInspectors.push(fieldInspector);                         }                         for each (var field:Field in featureLayer.layerDetails.fields)                         {                             if (outFields.indexOf(field.name) == -1)                             {                                 fieldInspector = new FieldInspector;                                 fieldInspector.featureLayer = featureLayer;                                 fieldInspector.visible = false;                                                                fieldInspector.fieldName = field.name;                                                                 attributeInspectorFieldInspectors.push(fieldInspector);                             }                                                   }                         editor.attributeInspector.fieldInspectors = attributeInspectorFieldInspectors;                         editor.attributeInspector.formFieldsOrder = AttributeInspector.FIELD_INSPECTOR_ORDER;                     }                     else                     {                         var formFieldsOrder:String = settingsObject.formFieldsOrder;                         if (formFieldsOrder)                         {                             editor.attributeInspector.formFieldsOrder = formFieldsOrder;                                               }                     }                     var singleToMultilineThreshold:Number = settingsObject.singleToMultilineThreshold;                     if (singleToMultilineThreshold && !isNaN(singleToMultilineThreshold))                     {                         editor.attributeInspector.singleToMultilineThreshold = singleToMultilineThreshold;                     }                     var showObjectID:String = settingsObject.showObjectID;                     if (showObjectID)                     {                         editor.attributeInspector.showObjectID = showObjectID == "true";                     }                     var showGlobalID:String = settingsObject.showGlobalID;                     if (showGlobalID)                     {                         editor.attributeInspector.showGlobalID = showGlobalID == "true";                     }                 }             } You would not have to set the <formfieldsorder> anymore with this update. Thank you very much for letting me know about this. It took care of my issues and i can move on to something else now. ... View more

Hi Jason - Have you ever seen this issue before? I tried your suggestion and it doesn't seem to be working for my printer set up. My 11x17 Landscape map prints the symbology fine, but my 11x17 Portrait maps run into the same problem you experienced before. I just running 10.1 service pack 1. Any other suggestions? Thanks, m Here is a link somebody posted earlier to me and it seemed to fix my issues. http://support.esri.com/en/knowledgebase/techarticles/detail/40538 I set my default on the server to our plotter and created a giant size custom size of 44x60. I have 24x36 layouts setup and wanted to make sure i dont have to deal with this issue later on so that why i went with that size. In the link above make sure to follow all of the steps carefully. And make sure you know which account the ArcGIS Server Service is running as in Services. Another thing to try is changing the DPI which i grabbed the code from this thread which helped on getting a better quality in the map. A big thanks to rhett for this bit of code. http://forums.arcgis.com/threads/71331-FV-3-advanced-print-widget-output-quality?highlight=dpi+setting Hopefully that will take care of your issues. ... View more

Jason,    I have done volumes of testing with printing landscape and it works great.  But the setting of landscape is not done in the code it is handled by the print engine. All you have to do is when the print dialog appears go into the preferences for the chosen print and choose landscape. Well that sounds like a easy fix. Thank you for your input on my question. ... View more

Jason: Are you printing the datagrid by itself?  Or are you able to print the datagrid along with the map? I am just printing the datagrid itself. The esearch widget you can set it up to print your search results and you can also setup the relates so you can print the related attributes as well. I would like to get both, search results datagrid and the related datagrid to both be landscaped by default. You could probably reference the MAP_ONLY in the print widget and maybe append or merge that to the search widgets printing of the datagrid or vice versa. but they would be on separate pages. Never attempted that yet. ... View more

At 3.1, it is NOT possible to exclude a layer within a map service, if specified the whole map service would be excluded Okay that is good to know. Are there any plans to add this to a future release? Sounds like i'll have to reorganize some map services on my end then. Also any idea on why i get lines thru my legend features? ... View more

Not the best approach maybe, but you could try this. I don't use the application builder but once you have the majority of the xml created with the builder you can go to that file on your computer or network and add in the formatting of the fields in to the xml with notepad or some other program. Save your changes, and then just right click and make the file read only and that should stop Application builder from modifying or deleting your information.  Of course you can't modify the file in application builder or notepad till you right click and uncheck the read only. But it should allow you to get it done and move on to other things. ... View more

Re: configuring pop-ups in 3.0: I'm under the impression that it's best to choose to configure the pop-up using either: 1) the Application Builder via the <description> tag -- I like this option because I can format my text using the HTML tags, OR 2) the XML <configuration> -- I like this option because I can use numeric and date formatting tags on FIELD values. I cannot see examples of how to either: 1) format date or number FIELDS within the <description> tag, OR 2) format non-field text without the <description> tag Following an example here, I can create the pop-up via the XML file, using <description> and <field> tags, like this: <configuration>    <title>Prioritized Tracts</title>    <description><![CDATA[   <br><i><b>Name:</b></i>  {TRACTNAME}    <br><i><b>GIS Acres:</b></i>  {GIS_ACRES}   <br><i><b>Salesforce:</b></i>  <a href="{SALESFORCE_URL}"> (Link) </a><br>]]></description>    <fields>    <field name = "GIS_ACRES">        <format usethousandsseparator="true"/>        <format precision="0"/>      </field>   </fields> </configuration> BUT, if I then view the code inside the Application Builder, all my field formatting gets deleted from the XML (everything below </description>)... this seems risky since I move between App Builder and configuration files. It seems safer to choose either <description> or <configuration>, rather than mixing the two, but I don't know how to do all the formatting I need using either option. Any advice is welcome. Oh, and my pop-up doesn't seem complicated, I need to be able to do these things: Name: Green Acres (bold/italics formatting on the left-hand column names) Acres: 2,550  (bold/italics formatting, and the FIELD needs precision and thousandsseparator formatting on its value) Date Protected: 2/3/2010  (bold/italics formatting, and the FIELD needs date formatting on its value) Under your fields tag add the following and change it to your data. Make sure to keep it false for visible and pick your dateformat you want but i think you are looking for shortDate. If you have that field for example INSTALLDATE in your description tag it will format the date using whatever you specified, for example shortDate.     <field name="INSTALLDATE" alias="Install Date" visible="false">         <format dateformat="shortDate"/>     </field> It has worked for me and should work for you as well. ... View more

I have this problem as well. So I have a feature class that had a date field in it. When this date field got populated it shows them like this, "11/13/12 11:23:57". I am now creating a web map using the ArcGIS Viewer for Flex, when I go into the configuration of the pop-up window I have the simple script of "<b>Date Collected: </b>{DateCollected}" along with listing a bunch of other fields. DateCollected is the field name. Then when I go to view this in the map is lists the "Date Collected: 1332340861000" I understand that I need to tell it to put that field in a particular format, I would like ShortDateShortTime. I just don't understand how to accomplish that. I have no html language/code experience and am learning as i go. The whole number is displays doesn't even look close to the date and time numbers. How do I get my date field to display correctly? If you are trying to format the date in the Description tag try this to get the short date. <description><![CDATA[<b>Date Collected: </b>{DateCollected}]]></description> <fields>     <field name="DateCollected" alias="Date Collected" visible="false">         <format dateformat="shortDateShortTime"/>     </field> </fields> I believe that is how i resolved the date in the popup. ... View more

Hi, Check function getLegendOptions() in ExportWebMapForm.mxml, it excluded BaseMapLayer by default. You can customize this function to exlcude other layers. Hope this helps. Rose Could you show a bit on how you excluded a layer out of an operational service?  Maybe if i can see how to exclude one layer i can figure out the rest of it out. thanks ... View more

Would you mind sharing where you changed the code at to accomplish this? I thought i had to do this thru the JSON for the print service but if you can only change it in the .MXML that would be a lot easier. Thank you. ... View more