EXTRACT FUNCTION

[jhakas29]

f_837I_ROUTING(EXTRACT(Subscriberrovider HL Loop:.:EDI_837I,1=1),PF_ROUTING)

what is meant by 1=1 ??

 

[BocaBurger]

Who wrote the rule? You seem to be choosing (extracting) the Subscriber where 1=1. Is that the whole rule? Should start with an = sign.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[SeriesConsumer]

1 = 1 ist just an alternative way of writing (logial) true, i.e. there is no real condition to be met for the EXTRACT, thus returning the complete series.

Maybe there was a "real" condition in the past that became superfluous and the developer (carefully) decided to modify just the condition instead of taking out the whole EXTRACT statement.

 

[BocaBurger]

And carefully decided not to document it.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[jamessong]

Newbie question - typically how to store comments for mercator? Wrire them directly in the type trees and maps?

 

[SeriesConsumer]

Don't know what you mean by "store comments for mercator". You can include comments in rules in a C/C++ fashion, i.e. either single line comments using

// everything in this line following the two slashes is a comment

or multi line comments using

/* everything
between the slash/asterisk
pair is a comment */

 

[BocaBurger]

/*comment */ is the prefered method:

/*This rule intentionally equals none*/
=NONE



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[SeriesConsumer]

Why is /* */ the prefered method?

 

[janhes]

Because that's what is says in the manual.

 

[SeriesConsumer]

Well the documentation I can access doesn't tell anything about the single line comments but just displays the other (6.7.1). Okay, that might also be a definition of "prefered" ;-)

 

[janhes]

From the 6.7.1 Map Designer manual

Comments in Map Rules
You can add inline comments to map rules. Comments do not affect how map
rules are evaluated. A comment may appear anywhere in a rule, as long as it does
not separate object names.
A comment is identified with the start characters /*. While the end characters */
can be present, they are not required. If the end characters are not present,
everything up to the end of that rule is the comment.

The following map rule has two comments, which are indicated by blue text:
= EXTRACT (Record:Customers /*Extract the Records */,
State Field:.:Customers = "FL" /* Get only the customers in
Florida */ )

 

[BocaBurger]

Personally, I prefer the comments before the rule. Embedding them in the rule can make it difficult to read.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!