Summary field in Info Object
See original GitHub issueSeveral objects have both a description
and a summary
field. The distinction seems to be that summaries are plaintext and should be <= 120 chars, while descriptions are markdown and can be arbitrarily long.
I’d like to have an optional summary
field in the Info Object e.g. for display in API Galleries. Currently to achieve this on AnyAPI we strip HTML/md out of the description
field and truncate it, which isn’t great.
I’d also like to see a higher level note about summary
vs. description
and add the “SHOULD be <= 120 characters” to each summary field (right now it’s just mentioned on operation.summary
)
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Roll-Up Summary Field - Salesforce Help
A roll-up summary field calculates values from related records, such as those in a related list. You can create a roll-up summary field...
Read more >How to create a Roll-Up Summary field on the Contact object
Create a Roll-Up Summary field on the Academic Profile object. Select Setup and search for Fields. Under Contact Custom Fields & Relationships, select...
Read more >Modeling with Fields Instead of InfoObjects - SAP Help Portal
Objects in SAP BW∕4HANA can be modeled with InfoObjects or with fields. Modeling InfoObjects brings additional effort, but offers a number of advantages....
Read more >Summary Object Details - TechDocs - Broadcom Inc.
Specify one to five fields as the key for each summary group. ... Specify a key field, the step size, and optionally the...
Read more >Create Roll-up Summary Fields Using Salesforce Flow
A roll-up summary field is one that aggregates data from a child object to a parent object that shares a Master-Detail relationship. Roll-up ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Revamping the thread, as after many ramblings I had to add an
x-summary
to my definitions.Proposal:
info.summary
to be a service description (eg. for catalog purposes)To make an analogy with a product:
It’s a minor (non breaking) change so the
v3.1-dev
branch would be the one.