xpxReadStepFileEx

xpxReadStepFileEx(repositoryName, modelName, headerModelRepositoryName   : STRING;   
                  headerModelName, STEPfile, logFile                     : STRING;   
                  shortNamesFile, schemaName                             : STRING;
                  options                                                : INTEGER;
                  VAR modelId                                            : GENERIC;
                  VAR warnings, VAR errors, VAR sdaiError                : INTEGER)
                  status

The xpxReadStepFileEx function is used to create a new model and populate the model with data from the specified STEP Physical File.

Arguments

1	Type	Name	Comment
2	STRING	repositoryName	Name of the repository where the new created model will be located
3	STRING	modelName	The name of the sdai_model that will be created and populated as a result of the xpxReadStepFileEx function
4	STRING	headerModelRepositoryName	A STEP Physical File consist of a Header Section and a Data Section. If a sdai_model of the Header Section should be created and populated during the xpxReadStepFileEx operation, then the headerModelName specifies the name of this sdai_model in the database. This model will be located in the repository specified by the repositoryName argument. This argument can be set to an empty string or indeterminate (question) when no creation and population of a STEP Physical File Header Section model is wanted
5	STRING	headerModelName	Specifies the name of the STEP Header model to be created and populated. The model must have a name that is unique within the repository that holds the model. The model name must start with a letter and the rest of the model name can be any mix of alphanumeric characters and the underscore character. Model names are case sensitive.
6	STRING	STEPfile	The name of the actual STEP Physical File to read into the database
7	STRING	logFile	The name of the file where logging from the xpxReadStepFileEx function will be recorded in case logging is enabled. This argument can be set to an empty string or indeterminate (question) when no logging should be performed
8	STRING	schemaName	The name of the Express schema that defines the structure of the data in the Data Section of the actual STEP file is found in the attribute FILE_SCHEMA.SCEMA_IDENTIFIERS in the Header Section of the STEP file. This schema will be used as the underlying schema of the new data model resulting from this command, hence this Express schema must exist as a dictionary model in the EDMdatabase when the xpxReadStepFileEx function is invoked.
9	STRING	shortNamesFile	The name of a file that contains short entity names of the actual schema that defines the data on the STEP file to be read. A STEP file can be written using the entity names specified in the Express schema that defines the sdai model that is mapped to the STEP file, or a STEP file can be written using short entity names. In case the actual STEP file is written using the short entity names, the shortNamesFile argument must specify a file that contains the mapping from short entity names to the entity names defined in the underlying Express schema of the actual sdai model.
10	INTEGER	options	same as edmiReadStepFile, except for the XPX prefix
11	GENERIC	modelId	destination model id
12	INTEGER	warnings	Number of warnings detected during reading the specified step file.
13	INTEGER	errors	Number of errors detected during reading the specified step file.
14	INTEGER	sdaiError	If the xpxReadStepFileEx operation is terminated due to errors in accessing the database, the argument sdaiError will receive the actual sdaiErrorCode causing the termination of the xpxReadStepFileEx operation.

Return Value

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'US:_r_XPX_Return_Value'.

Options

Option	Comment
XPXOption	comment

Example

<Missing Example>

Arguments

Return Value

Options

Example

See also

Filter by label