SObject fields rendered into OST without expected namespace

Issue #1119 resolved
Scott Wells repo owner created an issue

Opening this to track further progress on an issue reported by Yaroslav Trofimov where SObject fields that should have a certain namespace are being rendered into the OST without that namespace. This behavior started in 1.0.3.1 with the change to render fields into the OST with the full name to prevent collisions with same-named fields from other namespaces (including the default namespace).

Comments (4)

  1. Scott Wells reporter

    Evidently this build fixes the issue. I can't explain how/why, though. Likely more investigation required at some point, but the user has reported the issue as resolved.

  2. Scott Wells reporter
    • changed status to open

    Reviewing the log supplied by the user, it appears that 2.0.3.0 was installed instead of the test build attached here.

  3. Log in to comment