Closed FrankNeeckx closed 3 years ago
Pushed a fix for this issue. It will be made available in the next release of mdAL (and its corresponding VS Code extension).
Great I'm looking forward to test more of this nice product.
Met vriendelijke groeten, Sincères salutations, With kind regards, Frank
Frank Neeckx | project team t: +32 9 296 31 14
[Herbekijk de webinars voor projectontwikkelaar, bouwbedrijf en installateur]https://www.astena.be/nl/erp-software/kennisbank-erp
[cid:image002.png@01D6DC6F.14DC22A0]https://www.astena.be/nl/erp-software/
Van: Jonathan Neugebauer notifications@github.com Verzonden: zondag 27 december 2020 14:26 Aan: mdal-lang/mdal mdal@noreply.github.com CC: Frank Neeckx fn@astena.be; Author author@noreply.github.com Onderwerp: Re: [mdal-lang/mdal] Using spaces in Master-Name generates problems in setup page (#22)
Pushed a fix for this issue. It will be made available in the next release of mdAL (and its corresponding VS Code extension).
- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmdal-lang%2Fmdal%2Fissues%2F22%23issuecomment-751467826&data=04%7C01%7Cfn%40astena.be%7C86b45bccf07b48e51c3e08d8aa6affb1%7C3ba1c4379a2d41c2a5f72fcfd6217183%7C0%7C0%7C637446723823590204%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=t9ImB8nC0g5leH3aTXKtOhN3nKTmpesZW3OETT24kjM%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC2WJ6BG3WYEA4IA4EVU7GTSW4YXXANCNFSM4VD7PRLQ&data=04%7C01%7Cfn%40astena.be%7C86b45bccf07b48e51c3e08d8aa6affb1%7C3ba1c4379a2d41c2a5f72fcfd6217183%7C0%7C0%7C637446723823600197%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=h9JLXk95wpWKjFxF1dT821w1RHLKHdHFU%2B3%2Fwg1%2Bt5w%3D&reserved=0.
When using a master like :
master "Real Estate Unit" { ShortName = "REUnit";
This will generate a setup table definition with : field(2; "RealEstateUnit Nos."; Code[20]) { Caption = 'RealEstateUnit Nos.'; TableRelation = "No. Series";
But in the page definition you will get : field("Real Estate Unit Nos."; "Real Estate Unit Nos.") { ApplicationArea = All; }