LINQ in Grooper - Revision history

Dgreenwood: Dgreenwood moved page LINQ to Grooper Objects (Concept) to LINQ in Grooper without leaving a redirect

2025-10-15T14:22:32Z

Dgreenwood moved page LINQ to Grooper Objects (Concept) to LINQ in Grooper without leaving a redirect

← Older revision	Revision as of 09:22, 15 October 2025
(No difference)

Randallkinard at 21:22, 21 November 2024

2024-11-21T21:22:25Z

← Older revision		Revision as of 16:22, 21 November 2024
Line 87:		Line 87:
	Before ''''''Grooper''' 2.9''' '''LINQ''' expressions were not available.		Before ''''''Grooper''' 2.9''' '''LINQ''' expressions were not available.
	<!--#endregion-->		<!--#endregion-->

	~~== Glossary ==~~
	~~<u><big>'''Batch Folder'''</big></u>: {{#lst:Glossary\|Batch Folder}}~~

	~~<u><big>'''Batch Process'''</big></u>: {{#lst:Glossary\|Batch Process}}~~

	~~<u><big>'''Batch'''</big></u>: {{#lst:Glossary\|Batch}}~~

	~~<u><big>'''Data Column'''</big></u>: {{#lst:Glossary\|Data Column}}~~

	~~<u><big>'''Data Field'''</big></u>: {{#lst:Glossary\|Data Field}}~~

	~~<u><big>'''Data Section'''</big></u>: {{#lst:Glossary\|Data Section}}~~

	~~<u><big>'''Data Table'''</big></u>: {{#lst:Glossary\|Data Table}}~~

	~~<u><big>'''Expressions'''</big></u>: {{#lst:Glossary\|Expressions}}~~

	~~<u><big>'''LINQ to Grooper Objects'''</big></u>: {{#lst:Glossary\|LINQ to Grooper Objects}}~~

	~~<u><big>'''Review'''</big></u>: {{#lst:Glossary\|Review}}~~

Randallkinard at 14:58, 27 August 2024

2024-08-27T14:58:05Z

@@ Line 10: / Line 10: @@
 |}
 <br clear=all>
 <!--#region About-->
 ==About==
@@ Line 109: / Line 88: @@
 <!--#endregion-->
-[[Category:Articles]]
+== Glossary ==
-[[Category:Version 2.90]]
+<u><big>'''Batch Folder'''</big></u>: {{#lst:Glossary|Batch Folder}}

Randallkinard at 15:19, 10 May 2024

2024-05-10T15:19:43Z

@@ Line 9: / Line 9: @@
 |style="font-size:18pt"|'''&#128526;'''||''Special thanks to BIS team member Brian Godwin for contributing this article!''
 |}
 <!--#region About-->

Randallkinard at 19:58, 23 April 2024

2024-04-23T19:58:49Z

← Older revision		Revision as of 14:58, 23 April 2024
Line 1:		Line 1:
	~~<!--#region intro-->~~
	[[Image:Linq_to_grooper_objects_001.png\|thumb\|300px\|Language Integrated Query (LINQ, pronounced "link") is a Microsoft .NET Framework component that adds native data querying capabilities to .NET languages, originally released as a major part of .NET Framework 3.5 in 2007.]]		[[Image:Linq_to_grooper_objects_001.png\|thumb\|300px\|Language Integrated Query (LINQ, pronounced "link") is a Microsoft .NET Framework component that adds native data querying capabilities to .NET languages, originally released as a major part of .NET Framework 3.5 in 2007.]]
	~~<section begin="glossary" />~~
	<blockquote>		<blockquote>{{#lst:Glossary\|LINQ to Grooper Objects}}</blockquote>
	~~Using '''[https~~:~~//en.wikipedia.org/wiki/Language_Integrated_Query Language-Integrated Query (~~LINQ~~)]''' within '''~~Grooper~~''' Expressions~~
	</blockquote>
	~~<section end="glossary" />~~
	Expressions play an important role in '''Grooper''', so users often ask how to add writing expressions to their skillset. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, '''LINQ''' nets the same result while being more concise, readable, and overall, more user-friendly.		Expressions play an important role in '''Grooper''', so users often ask how to add writing expressions to their skillset. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, '''LINQ''' nets the same result while being more concise, readable, and overall, more user-friendly.

Line 13:		Line 10:
	\|}		\|}

	~~<!--#endregion-->~~
	<!--#region About-->		<!--#region About-->
	==About==		==About==

Randallkinard: Randallkinard moved page LINQ to Grooper Objects to LINQ to Grooper Objects (Concept): new naming convention

2024-04-17T19:21:19Z

Randallkinard moved page LINQ to Grooper Objects to LINQ to Grooper Objects (Concept): new naming convention

← Older revision	Revision as of 14:21, 17 April 2024
(No difference)

Dgreenwood at 18:33, 9 January 2024

2024-01-09T18:33:00Z

← Older revision		Revision as of 13:33, 9 January 2024
Line 1:		Line 1:
	<!--#region intro-->		<!--#region intro-->
	[[Image:Linq_to_grooper_objects_001.png\|thumb\|300px\|Language Integrated Query (LINQ, pronounced "link") is a Microsoft .NET Framework component that adds native data querying capabilities to .NET languages, originally released as a major part of .NET Framework 3.5 in 2007.]]		[[Image:Linq_to_grooper_objects_001.png\|thumb\|300px\|Language Integrated Query (LINQ, pronounced "link") is a Microsoft .NET Framework component that adds native data querying capabilities to .NET languages, originally released as a major part of .NET Framework 3.5 in 2007.]]
	<section begin="~~linq_glossary~~" />		<section begin="glossary" />
	<blockquote>		<blockquote>
	Using '''[https://en.wikipedia.org/wiki/Language_Integrated_Query Language-Integrated Query (LINQ)]''' within '''Grooper''' Expressions		Using '''[https://en.wikipedia.org/wiki/Language_Integrated_Query Language-Integrated Query (LINQ)]''' within '''Grooper''' Expressions
	</blockquote>		</blockquote>
	<section end="~~linq_glossary~~" />		<section end="glossary" />
	Expressions play an important role in '''Grooper''', so users often ask how to add writing expressions to their skillset. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, '''LINQ''' nets the same result while being more concise, readable, and overall, more user-friendly.		Expressions play an important role in '''Grooper''', so users often ask how to add writing expressions to their skillset. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, '''LINQ''' nets the same result while being more concise, readable, and overall, more user-friendly.

Dgreenwood at 19:43, 8 January 2024

2024-01-08T19:43:31Z

← Older revision		Revision as of 14:43, 8 January 2024
Line 1:		Line 1:
	<!--#region intro-->		<!--#region intro-->
	[[Image:Linq_to_grooper_objects_001.png\|thumb\|300px\|Language Integrated Query (LINQ, pronounced "link") is a Microsoft .NET Framework component that adds native data querying capabilities to .NET languages, originally released as a major part of .NET Framework 3.5 in 2007.]]		[[Image:Linq_to_grooper_objects_001.png\|thumb\|300px\|Language Integrated Query (LINQ, pronounced "link") is a Microsoft .NET Framework component that adds native data querying capabilities to .NET languages, originally released as a major part of .NET Framework 3.5 in 2007.]]
	<~~blockquote style~~="~~font-size: 16pt~~">Using '''[https://en.wikipedia.org/wiki/Language_Integrated_Query Language-Integrated Query (LINQ)]''' within '''Grooper''' Expressions</blockquote>		<section begin="linq_glossary" />
			<blockquote>
			Using '''[https://en.wikipedia.org/wiki/Language_Integrated_Query Language-Integrated Query (LINQ)]''' within '''Grooper''' Expressions
			</blockquote>
			<section end="linq_glossary" />
	Expressions play an important role in '''Grooper''', so users often ask how to add writing expressions to their skillset. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, '''LINQ''' nets the same result while being more concise, readable, and overall, more user-friendly.		Expressions play an important role in '''Grooper''', so users often ask how to add writing expressions to their skillset. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, '''LINQ''' nets the same result while being more concise, readable, and overall, more user-friendly.

Dgreenwood at 22:19, 9 December 2022

2022-12-09T22:19:52Z

← Older revision		Revision as of 17:19, 9 December 2022
Line 88:		Line 88:
	Before ''''''Grooper''' 2.9''' '''LINQ''' expressions were not available.		Before ''''''Grooper''' 2.9''' '''LINQ''' expressions were not available.
	<!--#endregion-->		<!--#endregion-->

			[[Category:Articles]]
			[[Category:Version 2.90]]

Dgreenwood: /* Applying LINQ to Grooper Expressions */

2021-04-08T16:44:49Z

Applying LINQ to Grooper Expressions

← Older revision		Revision as of 11:44, 8 April 2021
Line 75:		Line 75:
	# To populate a Boolean (true/false) field denoting whether any provider is outside Oklahoma		# To populate a Boolean (true/false) field denoting whether any provider is outside Oklahoma
	#: <code>(<span style="color:#0000ff">from</span> provider <span style="color:#0000ff">in</span> Demographic_Data.Insurance_Info <span style="color:#0000ff">where</span> provider.Provider_State <> <span style="color:#990000">"OK"</span> <span style="color:#0000ff">select</span> provider).Any()</code>		#: <code>(<span style="color:#0000ff">from</span> provider <span style="color:#0000ff">in</span> Demographic_Data.Insurance_Info <span style="color:#0000ff">where</span> provider.Provider_State <> <span style="color:#990000">"OK"</span> <span style="color:#0000ff">select</span> provider).Any()</code>
			====LINQ Example - Multi-instance Data Section ====
			For the following example, "Invoice Number" is a '''Data Field''' in a multi-instance '''Data Section''' named "Invoice Section" (As in there is more than one section repeated through the same document. i.e. There will be multiple "Invoice Number" '''Data Field''' results collected, one for every section).
			: <code>String.Join("\|", <span style="color:#0000ff">From</span> sec <span style="color:#0000ff">In</span> Invoice_Section <span style="color:#0000ff">Select</span> sec.Invoice_Number)</code>
			:* Concatenates all values from the field "Invoice Number" in the multi-instance section "Invoice Section", with pipe delimiter ("\|").
	====LINQ Example - Batch Process====		====LINQ Example - Batch Process====
	For the following example, a Should Submit expression is used to send any batches (or potentially folders) through an attended Review activity if it contains any “Generic” documents. This Should Submit expression would be written on the Review step. Note the DirectCast method which sets Item to its specific type (Batch Folder) which provides properties and methods available to objects of BatchFolder.		For the following example, a Should Submit expression is used to send any batches (or potentially folders) through an attended Review activity if it contains any “Generic” documents. This Should Submit expression would be written on the Review step. Note the DirectCast method which sets Item to its specific type (Batch Folder) which provides properties and methods available to objects of BatchFolder.
Line 80:		Line 84:
	<!--#endregion-->		<!--#endregion-->
	<!--#region Version Differences-->		<!--#region Version Differences-->

	==Version Differences==		==Version Differences==
	Before ''''''Grooper''' 2.9''' '''LINQ''' expressions were not available.		Before ''''''Grooper''' 2.9''' '''LINQ''' expressions were not available.
	<!--#endregion-->		<!--#endregion-->

← Older revision		Revision as of 16:22, 21 November 2024
Line 87:		Line 87:
	Before ''''''Grooper''' 2.9''' '''LINQ''' expressions were not available.		Before ''''''Grooper''' 2.9''' '''LINQ''' expressions were not available.
	<!--#endregion-->		<!--#endregion-->

	~~== Glossary ==~~
	~~<u><big>'''Batch Folder'''</big></u>: {{#lst:Glossary\|Batch Folder}}~~

	~~<u><big>'''Batch Process'''</big></u>: {{#lst:Glossary\|Batch Process}}~~

	~~<u><big>'''Batch'''</big></u>: {{#lst:Glossary\|Batch}}~~

	~~<u><big>'''Data Column'''</big></u>: {{#lst:Glossary\|Data Column}}~~

	~~<u><big>'''Data Field'''</big></u>: {{#lst:Glossary\|Data Field}}~~

	~~<u><big>'''Data Section'''</big></u>: {{#lst:Glossary\|Data Section}}~~

	~~<u><big>'''Data Table'''</big></u>: {{#lst:Glossary\|Data Table}}~~

	~~<u><big>'''Expressions'''</big></u>: {{#lst:Glossary\|Expressions}}~~

	~~<u><big>'''LINQ to Grooper Objects'''</big></u>: {{#lst:Glossary\|LINQ to Grooper Objects}}~~

	~~<u><big>'''Review'''</big></u>: {{#lst:Glossary\|Review}}~~