Hi, that error means the engine didn't find attribute 41 in its runtime script symbol collection, and those symbols get built from the attributes of the tax type that the use case belongs to. So I'd check first whether attribute 41 really sits under the GST tax type, whether it's part of the use case version you have released, and whether the field mapping is correct. If it hangs under another tax type the script will never see it.
On the values, for an option attribute mapped to a reference field BC does populate them from the field's option string when that field is validated. But you extended the enum after the attribute already existed, so the stored values could be stale. Worth opening the value list and revalidating the field, not saying that's the cause, just easy to rule out.
Bigger thing, the GST subscribers work on the standard document types, so posting and GST entries won't follow a new one.
Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis
