Pulling list property into a module
Appreciate that it is recommended to avoid using properties in lists, however we do have a couple of instances of this in our model.
Just looking to pull one of these into a module that we have already created, shown below and was looking for advice as to what formula is best to try and achieve this.
Best Answers
-
Should just be <'list name'>.<'property'>, assuming you've matched the formats.
I can't see your list name but assuming it was called 'GL', the logic would be 'GL'.'statement category'
There's a few reasons for not using list properties, namely versioning (as you can't version list properties) and also centralising attributes in a system module, but not the end of the world.
0 -
Without knowing the dimensionality of your model, I'd be curious of the relationship between your list 'GL Codes' vs 'Entity CC GL Cur' (in your 'Applies To…' column).
Is 'GL Codes' a subset of 'Entity CC GL Cur', or a completely different list? If different, this would be the reason and you'd likely need to do a LOOKUP against DAT01 GL Data Import.GL Code to retrieve the appropriate IS_BU from the list GL Codes. You'd also need to change the Applies to… to match the module.
e.g. GL Codes.statement category[LOOKUP:GL Code]
I'm making an assumption based on the screenshots, but hopefully this helps.
1
Answers
-
Not sure whether original screenshot was displaying correctly or not.
0 -
@luke_e thank you for the help, at first glance this seemed to work but then I've realised that it seems to be putting Balance Sheet down against every line, shown below, even though in the list I can see them distinct.
0
