
I'm very new to MS Dynamics SL 2018 and have been slowly figuring things out. My latest issue revolves around Subaccounts. Our subaccounts are made up of 4 segments, and the issue revolves around segment 3.
I have an old printout from the former user which shows the first page of all the Segment IDs and Descriptions that used to be listed when you looked up the info for Segment 3 (our Job Code portion of the subaccount).
I was hoping to add a new Job Code, but wasn't sure where to even find this info. I finally found where to view the Flexkey Table Maintenance, and after entering Segment Number 3 in the box, the table only showed 6 newer IDs when we had over 40+ on the list previously. I don't think I did anything to delete the old IDs, but all of them that I could see on my old printout (1st page only) are gone.
I'm familiar with Sage software and how data is stored, so I was wondering if the Segment ID for segment number 3 of the Subaccount is stored in a specific file, and see if I can get a backup of that file with the old data and swap it out with the current file (if that's even an option).
What's odd is that I don't think the loss of all the other Segment IDs has impacted the current subaccounts in use. ?
I hope I explained that all correctly. Any help would be greatly appreciated.
Thanks!
The SL App database has 2 related tables: FlexDef and SegDef. The Flexdef record with the caption "Subaccount" has the segment definitions (size, title, validation). The SegDef table has the actual values used to validate the entries. From your description running a select statement on the SegDef table where SegNumber = 3 should return all of the expected rows. If those values have been deleted, a restore of just that table could be performed, preferably to another temp DB image with a copy of the desired records from the SegDef table to the production App DB via SSMS.
Unless validation is turned on in Shared Information - Flexkey definition, user entries will be permitted without checking the entries in Shared Information. Validation may be enforced for individual subaccount segments. Changes are preferably made through the SL user interface, as that can help keep you from unintended consequences of system changes.