Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

intent: a roll-up cannot read the injected file / audit columns of a function: Attachment child (latest StoragePath by CreatedAt -> 422)

オープン
  • 何か問題がありますか？
#7,947 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
java
領域
api, backend

調査の方向性

Start with the roll-up validation path and EdmIntentGenerator.attachmentProperties, which the issue identifies as injecting attachment metadata after authored fields are validated. Trace how the generator builds roll-ups and how audit columns are added, then check whether StoragePath and CreatedAt are recognized for a function: Attachment child. Done means the latest roll-up in the example is accepted and generated, or the print feeder resolves the documented extra relation hop.

索引モデルが issue の本文から書いたものです。

説明

The gap

A print template reaches a cross-model record one hop away ({{document.Company.<Field>}}, PrintFeederSupport: cross-model depth 1). A company's logo uploaded as a function: Attachment child (CompanyLogo) is therefore two hops from an invoice (document.Company.<logo row>.StoragePath) and cannot be printed. The natural declarative bridge is a roll-up that mirrors the newest upload's path onto the parent:

entities:
  - name: Company
    fields:
      - { name: logo, type: string, length: 1000, readOnly: true }
  - name: CompanyLogo
    function: Attachment
    relations:
      - { name: Company, kind: manyToOne, to: Company, composition: true, required: true }
rollups:
  - { name: latestLogo, entity: CompanyLogo, via: Company, field: logo, op: latest, of: StoragePath, by: CreatedAt }

On 14.93.0 the generate answers 422:

rollup [latestLogo] of [StoragePath] is not a field of [CompanyLogo]
rollup [latestLogo] by [CreatedAt] is not a field of [CompanyLogo]

The file-metadata columns (FileName, ContentType, FileSize, StoragePath, Uuid) and the implicit audit columns (CreatedAt, ...) of a function: Attachment child are injected by the EDM generator (EdmIntentGenerator.attachmentProperties), after the parser has validated the roll-up against the authored fields only.

Ask

Either of:

  1. The roll-up validation (and its generator) knows the injected columns of a file child (and the audit columns of an audited / file-child entity), so op: latest, of: StoragePath, by: CreatedAt is accepted; or
  2. the print feeder descends one more hop into a cross-model record's to-one relations / file children (the "documented follow-up" in PrintFeederSupport), so {{document.Company.Logo.StoragePath}} resolves.

(1) is the smaller change and also serves "latest attachment" mirrors in general (a product's photo, an employee's signed contract).

Where it comes from

BusinessIntents billing: the issuer's logo on invoices / credit notes / debit notes / proformas (#7024 shipped the <image> resolver). Today the tenant has to place Templates/Company/<company id>/logo.png through the Documents perspective by hand; the module wants an upload on the Company record.

🤖 Generated with Claude Code

主要言語
Java
スター
278
フォーク
97
平均マージ
19時間 30分
マージ済み PR（30日）
242

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

eclipse-dirigible/dirigible のほかの issue

eclipse-dirigible/dirigible の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。