Thank you for your response.
The term "spin" may be somewhat more of a local term to my group
as I don't see it in the Dassault documentation; I didn't realize
that so I apologize, but I wasn't it wasn't intended to refer to a
git commit. The 3DX config files are known as "Spinner" (Dassault
refers to them as Spinners in their documentation, they are
natively *.xls files, which are really tab delimited files and not
excel). When they are imported into the schema, we call the
following MQL (Matrix Query Language) command (recommended by
Dassault in their documentation) that references a Dassault out of
the box JPO (Java Process Object):
exec prog SpinnerImport content=schema;
When this command is called, the framework digests only the rows
declared; it does not clear out existing rows that haven't been
declared in the imported file (additive only). This allows us to
create reduced spinner files to declare only the
changed/added/deleted rows related to our ticket for significantly
reduced spinner processing time. Our group has opted to use the
Spinners in this fashion for developer efficiency.
This is not a Git problem in nature; it is more related to our
group's practices in how we've chosen to use the files (working
with reduced for efficient processing rather than the whole
spinners) due to the nature of the 3DX framework. Using the files
in this fashion makes publishing the changes to git challenging
(more manual in nature without the assistance of a custom
This spinner concept is not new; Dassault has been using the
spinner files in this fashion since at least M1 (the predecessor to
their 3DX product). Since this issue has existed for a while, I
figured our chosen practice may not necessarily be unique to our
group and it was possible other groups may be operating in a
similar fashion but might have done something to solve the
predicament. If there is a simple solution short of devising our
own custom tool, I thought posting to this forum would be an
appropriate place to find said solution.
I don't believe the spinner files can be changed to binary for
improved processing (the command looks for *.xls), but I will look
in the documentation for clarification.
In terms of the server side .xls generation, that is a good
point and I have thought about that before as Dassault provides
this MQL command to export the DBs files:
exec prog SpinnerExport content=schema schematype=*
However, that command is difficult to use in terms of exporting
specific spinner files (i.e.: command lists "Valid schema types
are: [program, role, group, person, association, attribute, type,
relationship, format, policy, command, inquiry, menu, table,
webform, channel, portal, rule, interface, expression, page,
dimension, package, index, vault, store, site, location, server]"
but I have not found a way of generating the
SpinnerTriggerData_ALL.xls file separately on demand). When
requesting to generate all with a "*", it will then generate all
the spinners including the missing ones like trigger, but also
takes a while to export all of the spinner definitions (i.e.: last
time I clocked it was 37 minute 54 seconds, which isn't terrible).
I'm not ruling that out as part of the final solution, but there
should be simpler more efficient options.
I'm sorry if any of that was unclear before; this is my first
time posting to the forum and I wasn't sure what level of detail
was needed. This question was intended for other users who are
familiar with Spinner files and the challenges they face; please
let me know if more clarification is needed or if this post should
be moved to another section of the forum.