The next obvious step was to try and break the TEST layer. So created a new field with name of more than 31 characters. Then I tried downloading an offline area, the result was a fail with the same error.
Removed the troublesome field and I am able to download offline areas on my phone/iPAD.
A few other tests have confirmed this. It is the field length that causes the issue.
There is no limit (max 31 characters) in AGOL when you create a new field but when you try and download an offline area/replica then possibly that limit kicks in and the process fails.
You should avoid having field names this long, as some databases don't support it (e.g. ArcGIS Enterprise limitations are well documented in Survey123). It can be fine as you found out in ArcGIS Online. In ArcGIS Pro, you can add fields up to 64, but sometimes it limits it to 30 as well:
I would recommend going even further, and trying to keep your field names to 10 characters or less. This accommodates shapefiles. Even though they're a dated format, at some chance you may need to give to another user. So just avoid all future conflicts and keep your field names short, field aliases longer.
So from here, you can lodge a support ticket with Esri. They can address it in the documentation or otherwise identify it as a bug. From my perspective, you've already found out what the issue is, and can just bypass it and a bunch of other issues down the track by naming your fields shorter.
I just thought it was unexpected behaviour that ArcGIS Online allowed you to do this.
We have bypassed the issue by reducing length of the field names.
Just thought, I'd leave this here just in case anyone else finds this useful.
Ill also add here that this problem will occur when your hosted feature service schema contains attribute field names that are reserved Sqlite words. For example, a hosted feature service can have a field named "group". If you try and download this feature service in an offline area you will get the above error as "group" is a reserved sqlite word. See _keywords.html for all words that you should never use in AGOL as field names.
I have a content type with two fields, one pdf field which will be downloaded using the Download File module which provides a formatter (file download) to automatically download the pdf file with one click and one image field linked to the pdf field, using the Linked Field module. This works in the node without problems. The problem is when trying to rewrite the results of the image field in Views.I set the file field with the "File download fomatter" and exclude it from display.Then, I try to rewrite results of the image field like this
Depending on which Drupal 8 version you're using you'll see only the formatter File URI and you need to tick the option Display the file download URI to get the link you can use in an anchor href attribute later when overriding fields.
It would be good if anyone from ESRI could confirm if there was some sort of limit to the number of features with attachments or best practise with attachments. In my case I want as a read only reference layer a point layer which may have several hundred points each with a single photo attached. Is that asking too much of field maps?
So I decided to downgrade the image size of my attachments because when you click on a dot to see its attachment (in field maps) it does not appear to be a zoomable image. So I decided to resize the images to 800x600 pixels which significantly reduces the file size. This allowed the download to complete without error and I get to keep the whole dataset, no need to break it up into several "Map Areas".
I'm having the same issues described in this thread and have really been banging my head over what the issue could be... Everything was working fine then all of a sudden, our field staff are getting these download failures which I'm able to replicate. Map areas of a smaller size work fine but larger areas fail to download in Field Maps (both within the app and in the online map area creation).
Library Templates and Web Forms (collectively referred to as templates) are (parent) templates that generate individual (child) agreements. As such, they collect the field-level data for every agreement that is spawned from the template.
But my problem is along with the name of fields, I also want corresponding field lengths, field data types and field desciptions to be downloaded in excel file. What function module do I need to use to achive this ?
where /home/user/field_II/m_files contains the Field II m-files. Thisensures that the directory is included in the Matlab search path, and theuser-written m-files can then be placed in a separate directory.
Show them everywhere.
Load and display your custom field values in any theme template file with our hassle-free, developer friendly functions! Whether you need to display a single value or generate content based on a more complex query, the out-of-the-box functions of ACF make templating a dream for developers of all levels of experience.
Any Content, Fast.
Turning WordPress into a true content management system is not just about custom fields. Creating new custom post types and taxonomies is an essential part of building custom WordPress sites. Registering post types and taxonomies is now possible right in the ACF UI, speeding up the content modeling workflow without the need to touch code or use another plugin.
Simply beautiful and intentionally accessible.
For content creators and those tasked with data entry, the field user experience is as intuitive as they could desire while fitting neatly into the native WordPress experience. Accessibility standards are regularly reviewed and applied, ensuring ACF is able to empower as close to anyone as possible.
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
The responsibility for the upkeep of the fields at a local Little League program belongs to the local league board of directors. In many areas, the local league has an agreement with a municipality to maintain the fields.
Generally, the distance between base paths on fields for 12-year-olds and below in baseball and in all divisions of softball is 60 feet. A local Little League board of directors may opt to use a 50-foot diamond in the Tee Ball divisions. The distance in all divisions of baseball for 13-year-olds, is up to 90 feet, with a local league option to shorten the distance to 75 feet for Junior League Baseball and 70 feet for Intermediate (50/70) Baseball Division for regular season play.
Distance from the back of home plate to the outfield fence is a local league option, but the following distances are recommended: baseball, Major Division and below, 200 feet; Intermediate (50/70) Baseball is 200 feet and Junior and Senior League Divisions, is 300 feet. See playing rules for tournament distances. For girls softball, all divisions, 200 feet.
The Download Field adds an additional field type to your SobiPro component.
It allows users to upload files from the front-end (in the entry form) and download files (in the details view) for/of an entry of the used SobiPro section/directory with different access control. Use it to create a download section for your website or to simply let your visitors download a file (e.g. a price list, an inventory list or an e-book a.s.o.).
Field service management software is used in various industries by businesses that rely on streamlined management of their off-site operations. Such software typically supports customer service, maintenance, installations, and repairs. Sectors like utilities, industrial manufacturing, high-tech, telecommunications, and construction depend on field service management software for efficient scheduling, real-time communication, and optimized task allocation. This software enhances operational productivity and customer satisfaction across different industries.
Field service management software is essential for effective coordination of mobile teams and tasks. It optimizes scheduling, communication, and resource allocation, resulting in increased productivity, reduced costs, and improved customer satisfaction through timely and efficient field services.
To streamline field service management, use software that helps you centralize scheduling and dispatch, communicate in real-time, optimize routes, execute tasks, and generate insights with data analytics. These practices enhance operational efficiency and customer service in field operations.