This topic provides information on troubleshooting issues that you may encounter running the Aptify 67.4 0 or Aptify Web 67.4 0 setup.
| Note |
|---|
In some cases (as noted) it is recommended to re-run the setup on a restored backup taken from prior to installation. |
...
Troubleshooting issues with installing Aptify 67.4 0 are addressed in the following sub-topics:
- Installation Fails During Update of Orders Entity
- Circular References with Form Templates or Dashboard
- Scenarios Where Setup May Fail Due to Entity Updates and Required Fields
- Grant SQL Cannot Generate a Field that Does Not Exist in the Base View and Field Level Security
- Aptify Web Site May Fail to Load on Non-default IIS port
- Aptify Web Site May Fail to Load Certain DLLs
- Database Setup Fails Due to Enabled Row Set Security
- The "Create Order" button on Summary Forms may not work as Expected
- CC Account and CC Partial fields may appear together
If you experience an error not described below, please contact Aptify Technical Support for assistance.
| Anchor | ||||
|---|---|---|---|---|
|
If your organization has modified the Orders entity, it is possible that the Aptify 67.4 0 installation may fail when the setup program is updating the Orders entity while attempting to update virtual field definitions for the ShipToEmail and BillToEmail fields to support company only orders. Perform the following steps if the installation fails as described in this scenario.
...
| Anchor | ||||
|---|---|---|---|---|
|
The Aptify 67.4 0 database setup may fail if a form template or dashboard circular reference error is found. In Aptify 67.40, Aptify added the Unique Identifier for form templates to prevent circular reference errors, so you should not see this error on systems that originated from 67.40. However, you may see this issue if your database was at one point an earlier version.
...
- Identify which required field does not have a default value based on the error information provided by the setup program.
- Restore the database back to its original state prior to the installation attempt which failed.
- Open the appropriate entity and specify a default value for the field you identified in step 1.
- Save and close the entity.
- Re-run the Aptify 67.4 0 setup program.
| Anchor | ||||
|---|---|---|---|---|
|
If an entity has a field that is not part of the base view, the installation may fail. For example, Aptify 67.4 0 added a new field to Companies called Logo. This can be a problem for certain databases whose entity meets these conditions:
...
If an organization has an entity that meets all of the conditions listed above and the 67.4 0 setup program is adding or new field to that entity, then the 67.4 0 setup program will fail. The work around for the above example is:
...
When launching the Aptify website, certain 32-bit DLLs in the AptifyServicesAPI Bin folder may prevent the site from loading – most notably is ConfigManifestForm.dll, which may exist on systems that have been through a major version upgrade. The workaround is to remove these DLLs and any dependencies from the AptifyServiceAPI folders and then load the site again. Contact Aptify Technical Support if you have any questions or concerns about removing objects from the AptifyServiceAPI folder.
| Anchor | ||||
|---|---|---|---|---|
|
When upgrading to Aptify 67.40, the database setup fails if Row Set Security is set in the Persons and Companies entities in your environment. To ensure a successful upgrade, you should remove Row Set Security from the Persons and Companies entities before beginning the installation procedure. You can reinstate the Row Set Security settings once the install is successful. Follow these steps for the Persons and Companies entities:
...
Once you have completed the upgrade to Aptify 67.40, you can re-enable the rules for Row Set Security in the Persons and/or Companies entities using the following steps:
- Open the record for the entity in the Entities service.
- Click the Row Set Security tab.
- Open a new Row Set Security sub‐type record.
- Either click the New Record... button in the menu bar, or right‐click in the gray area and select New from pop‐up menu to open a new record.
- Enter the rule you are recording back in step 4 in the Base View Where Clause field.
- Enter a description for the rule.
- Click OK to save the rule.
- Enter additional rules for the same entity, if necessary. Aptify uses an AND operator to separate multiple Base View where Clauses within a generated base view.
- Alternatively, you can click OK and New in Step 8 to save the current and open a new Row Set Security record in one step.
Save and close the Entities record.
Regenerate the base view for any related entities that join to the entity for which you just enabled row set security.
...
After upgrading to Aptify 67.40, there might be a scenario where the 'Create Order' option from a person or company summary form may not work. Follow the below steps for the respective entity to make sure it works:
...
If you have records contain bad data, the setup may fail when the Database Objects validation options is selected in the setup. For example, if you have orders for a subscription with invalid Subscriber ID where that person (Subscriber ID) does not exist in the database hence failing the validation process. You will need to fix the invalid data before continuing with the install. The dialog that is displayed during the setup process when this error is encountered includes suggested SQL to resolve or further investigate the issue. See the appropriate step in the Installing Aptify 7.0 Server Software for more details.
| Anchor | ||||
|---|---|---|---|---|
|
While creating a new order, a SPM for a Company, or a Person's record etcetera, only the CC Account field should be visible to the users. After saving the record, only CC partial field should be visible to the users. In case if both the fields are displayed together, please follow the below process to rectify the same.
Run the Generate HTML5 Web Form Template UI Parts process flow (Process Flow ID:97) for Form template ID 18139, this rebuilds the HTML string and updates UIPart table. Please refer below image for reference: