![]() Even so, M tries to keep you safe here: If you ask the engine to evaluate a cyclic reference that it determines will never terminate, it will raise Expression.Error: A cyclic reference was encountered during evaluation. If the nefarious idea comes that maybe you could use a inclusive identifier reference to self-reference outside the context of a recursive function-say, to code up an expression like a = * 10-you’re treading on dangerous ice. Recommendation: Only use inclusive references when necessary. Unnecessarily using this style of reference might even cause confusion as the next developer reading your code might see the and then spend time puzzling over why you used it. In this record, what can the expression defining field a “see”? To put it in other words, what variables is the code that defines a able to reference?ī = * // while valid, neither is needed here - a * b works fine and is preferable For the moment, assume that the below is all that exists in your Power Query world (so there’s no standard library, no other queries and no global environment of any kind present as the mashup engine evaluates the expression).
0 Comments
Leave a Reply. |