2/22/2025 10:56:28 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
Value cannot be null. Parameter name: TypeName 
Posted: 25 Mar 08 7:39 PM
|
Has anyone seen this error after creating a new entity page/smart part, building, deploying then opening the new page in the SLX Customer Portal:
Value cannot be null. Parameter name: TypeName
It seems to be failing in the onload of the .aspx page when debugging, but stalls on the SLX login page. The new page must be navigated to from a link..
The page/smart part is based on a custom entity - extension off ticket. The page and smart part are based on the Ticket Entity. The failing smart part just has a few fields from the ticket extension - real basic.
There is a little more to this story, let me summarize that I deleted the smartpart and page at one point and started over. I moved the first smart part to VS and got the same error. I then went back and deleted everything, did a ctrl Build web platform, shut down the AA and started over. The second try I never moved the smartpart out of AA but am getting the same error.. |
|
|
|
Re: Value cannot be null. Parameter name: TypeName
Posted: 26 Mar 08 3:26 PM
|
| Solved! sort of.. I had created my new aspx page by right clicking and choosing 'entity page'. I tried the New Form Wizard and all is well. Not sure what I missed - not much to miss in the creation process. This is on record with SLX tech support. |
|
|
| |
|
Re: Value cannot be null. Parameter name: TypeName
Posted: 19 May 08 8:51 AM
|
I ran into this problem over the weekend on a custom page I was working on.
If your custom page was of type Sage.Platform.WebPortal.EntityPage, you need to make sure this code was implemented in your .aspx.cs file in your deployed folder, in the OnPreInit function.
//Apply Page Properties
PropertyConfigurationCollection pageProperties = new PropertyConfigurationCollection();
pageProperties.Add("EntityTypeName", "Sage.Entity.Interfaces.IAccount,Sage.Entity.Interfaces", "");
pageProperties.ApplyProperties(this);
Obv. the second parameter to pageProperties.Add changes depending on your Entity Type. I snagged the code out of account.aspx.cs.
Hope this helps someone in the future. |
|
|
|
Re: Value cannot be null. Parameter name: TypeName
Posted: 19 May 08 11:34 AM
|
You can set this is the AA without modifying the generated page (which is the way it is intended to be done anyway). For an entity page, you have to tell it which entity the page is for so it has context. You can do this by doing the following:
- Open the page in AA
- Go to the Advanced tab, you'll see the base Page Type is "Sage.Platform.WebPortal.EntityPage, Sage.Platform.WebPortal"
- Click the "Configure Base" button
- In the dialog that opens, locate the "Entity Type" property, and use the drop-down to select the *interface* for your entity. The result for the property will look like this "Sage.Entity.Interfaces.IAccount,Sage.Entity.Interfaces"
Make sense? Setting this property in the AA is what causes that code to be generated for the page.
-Ryan |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|