microsoft / microsoft/ALAppExtensions

[Change Request] table 311 "Sales & Receivables Setup" - field(31; "Logo Position on Documents"; Option)

Open
#29,518 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enum-request ext-ready-to-implement SCM
Dominant language
AL
Stars
988
Forks
692
Avg merge
49m
Merged PRs (30d)
1

Description

Why do you need this change?

We have to extend the Enum for additional Logo positions like full width etc.

Describe the request

Hello, can you please change the field 31 "Logo Position on Documents" in table 311 "Sales & Receivables Setup" from option to an Enum?

table 311 "Sales & Receivables Setup"
{
.
.
.
        field(31; "Logo Position on Documents"; Enum "Logo Position on Documents")
        {
            Caption = 'Logo Position on Documents';
            ToolTip = 'Specifies the position of your company logo on business letters and documents.';
        }
enum 59001 "Logo Position on Documents"
{
    Extensible = true;
 
    value(0; "No Logo")
    {
        Caption = 'No Logo';
    }
    value(1; Left)
    {
        Caption = 'Left';
    }
    value(2; Center)
    {
        Caption = 'Center';
    }
    value(3; Right)
    {
        Caption = 'Right';
    }
}

Internal work item: AB#616632

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating table 311, "Sales & Receivables Setup," and inspect field 31, "Logo Position on Documents," together with any references to its current option values. The change is complete when the field uses the extensible "Logo Position on Documents" enum and supports the listed logo positions without breaking existing usage.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.