Disable Data Standard in Frame Generator

Disable Data Standard in Frame Generator

jorge.pereira.01
Explorer Explorer
2,168 Views
6 Replies
Message 1 of 7

Disable Data Standard in Frame Generator

jorge.pereira.01
Explorer
Explorer

Hi,

 

Currently I have the behavior shown on this Video.

 

(view in My Videos)

 

And I am trying to disable Data Standard for Frame Generator, by using the following code:

 

 

function InitializeWindow {	

	#begin rules applying commonly
	$dsWindow.Title = SetWindowTitle		
	InitializeCategory
	InitializeNumSchm
	InitializeBreadCrumb
	InitializeFileNameValidation
	#end rules applying commonly

	$mWindowName = $dsWindow.Name
	switch ($mWindowName) {
		"InventorWindow" {
			#rules applying for Inventor
		}
		"AutoCADWindow" {
			#rules applying for AutoCAD
		}
		"InventorFrameWindow" {

			$dsWindow.add_Loaded({
					$dsWindow.CancelWindowCommand.Execute($this)
				})
					
		}
	}
	$global:expandBreadCrumb = $true	
}

 

 

But this crashes Inventor, when saving the frames files.

 

Also is possible to disable the "Generate File Number" Windows from Inventor?:

jorgepereira01_0-1678050030618.png

 

 

0 Likes
Accepted solutions (1)
2,169 Views
6 Replies
Replies (6)
Message 2 of 7

Markus.Koechl
Autodesk
Autodesk
Accepted solution

To disable VDS Frame Generator dialogs, you better rename or remove the file FrameGenerator.xaml. To avoid the VDS temporary file names for member files, you should enable Vault numbering for FG. Add the command AFG_CMD_ChangeProfile to the configuration file as shown below: 

MarkusKoechl_0-1678107027203.png

Generate Number Window: Which Vault Update level do you use? The latest update, 2023.2.1, has an issue disabling the Generate Number dialog as a default to be addressed in a future update. Keeping the update level 2023.2 is an alternate solution.



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes
Message 3 of 7

JPereiraASDK
Explorer
Explorer

Thank you. Renaming FrameGenerator.xaml, worked.

 

I have not seen any differences when editing dataStandard.InvAddIn.dll.config with that configs. What was suppose to happen?

 

Generate Number Window: Yes I am in 2023.2.1. I have migrated because the 2023.2 was adding _DS_FGM_ to the members name. So I think I will mantain the 2023.2.1.

0 Likes
Message 4 of 7

jgunter3JNFK
Participant
Participant

Hi Markus,

 

I am having issues using VDS when creating a part within an assembly. Once the part has been created, I cannot check in the file from the assembly. Do you know what might be causing this?

 

Component Create Error.gif

 

Thank you

0 Likes
Message 5 of 7

Markus.Koechl
Autodesk
Autodesk

@jgunter3JNFK : how does your question relate to the topic and solution of this thread? Anyway - its hard to say what might be wrong, as you don't share any insights on the project or Vault configuration. Does the default configuration behave the same? Which version and update level are you using?



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes
Message 6 of 7

jgunter3JNFK
Participant
Participant

Apologies if this is not the best place to post this. In Jorge's original video, he demonstrated creating the skeleton part in a similar way. I was hoping to discuss this with you since you seem very knowledgeable about the Data Standard. We are currently using Inventor (2022 5.3) and Vault (Pro 2022 5.1).

 

I was wondering if you have encountered this issue before, where a file can't be checked in within an assembly but can be when opening the part.

 

Sorry for any inconvenience and thank you for your time.

 

 

 

0 Likes
Message 7 of 7

jgunter3JNFK
Participant
Participant

@Markus.KoechlI found the solution, but not the reason why as we are not using and third party tools

 

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Error-The-followin...

 

I guess the ipj file will just need to be refreshed everytime we create a component within an assembly

0 Likes