Can you share a screenshot of the writer settings?

Hi @dan_mbc

​ I think you are on right track but we might need to use an AttributeValidator first.

Cause

The main reasons for such error messages are a mismatch between incoming data and the feature service's existing schema.

Resolution

This issue has been resolved in FME 2021.0 and newer. The string data get trimmed automatically based on the schema. 

For 2020.x and earlier

For this example, I have 3 attributes with data types of string (length 2), integer, and a DateTime field.

Right-click on ArcGIS Online/Portal writer → Show Summary Annotation

Check that the incoming attribute matches the schema on the writer using AttributeValidator

if the attribute fails the check you should get an error similar to this below 

Attribute 'string1' with value 'yes' fails to check for Maximum Length = 2 

To fix this use AttributeManager, StringExtractor, or DateTimeFormater to fix the data type before writing.

@Evaluate(@int8(@Value(string1)))  -- Convert data to Int8
@Substring(@Value(string2),0,49)   -- Trim string attribute length to 50 characters

@Evaluate(@int8(@Value(string1)))  -- Convert data to Int8
@Substring(@Value(string2),0,49)   -- Trim string attribute length to 50 characters

Thank you. 

I am currently on FME 2021.0.1.0, but, I think when I originally created this workbench I was on a 2020 version, then a week or two later I downloaded the new version. So this workbench might still be treated as a 2020 workbench? 

I am therefore following the workaround:

I used the AttributeValidator to firstly check all the string fields, and they all passed. I then checked the date fields and these failed. So it would appear these are the issue, and looking at it I think I can see why. The format for my OpenDateTime and ClosedDateTime field is as you'd expect, a date and a time, but the FME writer to Portal is just writing it as a date field. I can't see a way to change this in the writer settings, it only seems to offer date? 

I noticed in a previous workbench which also writes to Portal, I get options in writer to select  the types of field as 'esriFieldType', including esriFieldTypeDate, but I don't seem to have them options in this new workbench? Not sure if that would have helped or not? 

Anyway back to the workaround, I firstly deleted the feature layer in Portal. I have used the DateTimeConverter to convert them into the correct format and then ran the workbench. This ran as usual with no problems. I noticed still in the writer the datetime fields are still only showing as a date field type in the writer. 

I then re-ran the workbench but this fails with the same error. I think I expected this as there is still a mismatch between FME and Portal with the date field? Do I need to change the DateTimeConverter to output only as a date field (YMD), although the time info is useful?

I have attached some screenshots showing the updated section of workbench (including the show summary annotation) and also a screenshot of the DateTimeConverter.

Thanks 

Hi, attached is the settings.

Just to add to this, I decided to create a new workbench in version 2021 and repeat much of the existing workbench.

I managed to get it working and overwriting fine, however I realised I had removed the two fields with long character counts (details and locationspecifics). But my writer did include the datetime attributes, so the new workbench seemed to sort that issue with the dates. However once I added back in the details and locationspecifics fields, and written then tried to overwrite, it failed.

It mentioned in the warning about how the server was truncating the fields, but it still failed with the same error as above. I decided to use SubstringExtractor to make both them fields only 200 long, and that stopped the warnings but the error still remained.

I then used attribute manager (removed SubstringExtractor transformers) to trim the characters to 50 (as advised above) rather than using substringExtractor, using the values: @Substring(@Value(locationsspecs),0,49).

This had the desired result, the characters were only 50, but once written to Portal it then failed to overwrite.

Feel like I am getting closer, but not quite there.

Hi @rahulsharma​ , I don't suppose you have had chance to look at this?

I feel like this second workbench is closer to working but when I added in the two field with long character counts, it caused the usual error. Wondered if you had any ideas?

Hi @dan_mbc​ I have tried some DateTime data but it all works for me. I will escalate to a support ticket. You can provide me some sample data that we can try and possibly find a solution.

Conducted a screen share session with @dan_mbc​ and was able to resolve the issue.

BACKGROUND:

One of the attributes (string), contains some text with angle brackets (<, >), which are being interpreted as HTML tags when the translating or writing data to existing Portal Feature services, which causes an error on the server-side, and the features get rejected.

RESOLUTION: Replace Angle brackets

Option1 : Use StringReplacer transformer to remove the angle brackets

Option2: Use StringPairReplacer to replace <this> to (this)

@rahulsharma​ Does a document with known issues like this one exist?

Thanks again for your time Rahul, the workbench runs perfectly now.

I no doubt will encounter this problem again too, so was great to diagnose the problem.

Hi @nielsgerrits​ 

Currently, there is not one but our team is working on this, stay tuned.