Viewconfig location in the new web portal

Table = DialogUserConfiguration
See these posts for details:
Where do the application theme preferences get stored
Lost bookmarks after change of authentication method

Thank you very much for the quick answer. I am seeing that the config looks like a very long encrypted string. I am curious to find out how the apiserver interprets it and builds the config so I can manipulate it.

Do you know anything about that?

Run this query to view to B64 encoded 'DialogUserConfiguration.ConfigurationData' column and see the posts.

	SELECT u.Ident_QBMXUser
		,CONVERT(VARCHAR(MAX), CAST('' AS XML).value('xs:base64Binary(sql:column("ConfigurationData"))', 'VARBINARY(MAX)')) AS DialogUserConfiguration
	FROM DialogUserConfiguration
	JOIN QBMXUser u ON u.UID_QBMXUser = DialogUserConfiguration.UID_QBMXUser
	WHERE UID_DialogProduct IN (
			SELECT UID_DialogProduct
			FROM QBMProduct
			WHERE Ident_Product = 'WebDesigner'
			)

Thank you very much. You're a hero. Vey helpful.

While we are on the topic I wondered how the creation of the entry on DialogUserConfiguration works. The entry on the table is only created once the user logs in to the portal and I am wondering if there is a way to overwrite the inital configuration data as there is no onsaving script or template on this table.

The goal is to give all users the same initial config.

As always thank you very much.

While we are on the topic I wondered how the creation of the entry on DialogUserConfiguration works. The entry on the table is only created once the user logs in to the portal and I am wondering if there is a way to overwrite the inital configuration data as there is no onsaving script or template on this table.

The goal is to give all users the same initial config.

As always thank you very much.

I guess you could pre-stage the QBMXUser and DialogUserConfiguration entries for new Persons.
First create a Person called 'Default' log into the portal configure the setting to your likings.
Make a script or process that triggers after a Person is inserted that...
creates a new QBMXUser entry
and creates a new DialogUserConfiguration entry that takes to ConfigurationData of the 'Default' person you just configured
P.s. this is just off the top of my head ;-)