Similar error from previously posted question but we aren't using any DD4T template building blocks in the page/component templates
Deserialize DD4T content error while validating DXA Model service
We can successfully publish json, txt and xml to the Broker database but can't load the files in a browser.
2018-06-08 15:25:04,729 DEBUG c.s.d.m.s.ContentService - Trying to request a
page with localization id = '1109' and path = '/subdirectory/sample.json'
2018-06-08 15:25:05,177 DEBUG c.s.d.m.s.ContentService - Requested
publication 'xxxx', path '/subdirectory/sample.json', result is '[tcm:xxxx-
xxxxxx-xx]'
2018-06-08 15:25:05,419 INFO c.s.d.m.s.DefaultPageModelService - Found DD4T
model while requested R2, need to convert, no expansion needed, request
PageRequestDto(publicationId=1109, uriType=tcm,
path=/subdirectory/sample.json, includePages=INCLUDE, contentType=MODEL,
dataModelType=R2, expansionDepth=100,
depthCounter=com.sdl.dxa.common.dto.DepthCounter@9f)
2018-06-08 15:25:05,570 INFO o.d.d.s.j.TridionFieldTypeIdResolver -
Instantiating TridionJsonFieldTypeResolver for [simple type, class
org.dd4t.contentmodel.Field]
2018-06-08 15:25:05,607 INFO o.d.d.s.j.TridionFieldTypeIdResolver -
Instantiating TridionJsonFieldTypeResolver for [simple type, class
org.dd4t.contentmodel.Field]
2018-06-08 15:25:05,661 INFO o.d.d.s.j.TridionFieldTypeIdResolver -
Instantiating TridionJsonFieldTypeResolver for [simple type, class
org.dd4t.contentmodel.Field]
2018-06-08 15:25:05,672 INFO o.d.d.s.j.TridionFieldTypeIdResolver - Instantiating TridionJsonFieldTypeResolver for [simple type, class org.dd4t.contentmodel.Field]
2018-06-08 15:25:05,681 INFO o.d.d.s.j.TridionFieldTypeIdResolver - Instantiating TridionJsonFieldTypeResolver for [simple type, class org.dd4t.contentmodel.Field]
2018-06-08 15:25:05,690 ERROR o.d.d.b.j.JsonDataBinder - Error deserializing.
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "SampleField" (class org.dd4t.contentmodel.impl.PageImpl), not marked as ignorable (21 known properties: "Schema", "fileExtension", "CustomProperties", "lastPublishedDate", "Filename", "MetadataFields", "revisionDate", "Publication", "Folder", "Url", "OwningPublication", "Title", "Id", "Categories", "LastPublishedDate", "ExtensionData", "StructureGroup", "Version", "ComponentPresentations", "RevisionDate", "PageTemplate"])
at [Source: (String)"{
Formatting the JSON as suggested in the previous post didn't fix the issue. In 2013 we would publish these files directly to the file system. We were told that is not an option using Topology Manager in Web 8.5.