Export Asset Package does not include all sequences

[CarlVon_Stetten1]

The export asset package tool appears to examine the attribute rules of all the feature classes that are being exported and automatically includes any sequences that are explicitly named in attribute rules.

However, we have hundreds of sequences tied to map book grids so that new sewer structures are named using unique numbers per map grid.  The attribute rule dynamically calculates the sequence name based on the map grid polygon the structure is placed in, so the individual map grid number sequences are never explicitly named.

How can we get the export asset package tool to include those sequences?

[MikeMillerGIS · Accepted solution]

NextSequenceValue should require a string literal, so you need to make a switch yard that list out every call to NextSequenceValue using a string and not a variable.  Once you do this, the export AP and copy/paste and other functions will properly copy/export sequences.

Databases have hundreds of sequences by default, we do not want to blindly copy all of them.  So we rely on the requirement that NextSequenceValue uses a string literal.

[CarlVon_Stetten1]

It "should" require a string literal, but it does work if you pass a variable as the argument.  I had considered writing a "switch yard", but it would have 750 tests in it.  This same dynamically-driven sequence variable is used in attribute rules on sewer_device, sewer_junction, sewer_assembly, structure_junction, structure_boundary, and some custom feature classes.  And every time we expand our system into a previously undesignated map grid, we'd have to update all of those rules.

My current method of getting these 750 custom sequences into the asset package is to export an asset package and then run an FME workspace that compares the sequences defined within the asset package to the original EGDB and inserts the missing sequences into the sequences table.