Skip to content

Entity.xsd missing MaxSizeInKB and CanStoreFullImage for File/Image attributes #44

Description

@TomProkop

Problem

The Entity.xsd schema does not include MaxSizeInKB or CanStoreFullImage elements, causing txc ws validate to report XSD errors for File and Image attributes. Dataverse accepts these elements on import and they are valid metadata properties in the SDK (FileAttributeMetadata.MaxSizeInKB, ImageAttributeMetadata.MaxSizeInKB, ImageAttributeMetadata.CanStoreFullImage).

However, Dataverse SolutionPackager does NOT re-export MaxSizeInKB or CanStoreFullImage in Entity.xml — instead it uses <MaxValue> for the size. So the XSD is technically consistent with what SolutionPackager exports, but inconsistent with what Dataverse accepts on import.

Current workaround

The pp-entity-attribute template now uses <MaxValue> instead of <MaxSizeInKB> to avoid the XSD warnings.

Recommendation

Either:

  1. Add MaxSizeInKB and CanStoreFullImage to Entity.xsd as optional elements (since Dataverse accepts them), or
  2. Document that <MaxValue> is the correct element for File/Image size in solution XML

Evidence

  • SDK: FileAttributeMetadata.MaxSizeInKB (int), ImageAttributeMetadata.CanStoreFullImage (bool)
  • Maker export: uses <MaxValue>32768</MaxValue> for file, <MaxValue>10240</MaxValue> for image — no MaxSizeInKB
  • Entity.xsd: has <MaxValue> (type xs:double) but not MaxSizeInKB or CanStoreFullImage
  • XSD location: src/TALXIS.Platform.Metadata.Validation/Schemas/Entity.xsd

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions