To Do List FAQ - Intergraph Smart 3D - Troubleshooting

Intergraph Smart 3D Troubleshooting Reference

Language
English
Product
Intergraph Smart 3D
Subproduct
Troubleshooting
Search by Category
Troubleshooting
Smart 3D Version
12 (2018)

When fixing one To Do List message, occasionally more than one To Do List message is removed and sometime new To Do List messages are created. Why does this happen?

Occasionally, more than one To Do List message is created for a problem. For example, in a route application, an overlap is between two objects and two To Do List messages appear in the To Do List. So solving one message will solve the other.

When a To Do List message is solved, the dependent semantic is called. The To Do List message is resolved or a new one is created.

Why are the To Do List messages not solved during synchronization?

Synchronization does not solve To Do List messages, but semantics get triggered because of the change made in the catalog. When semantics get triggered, To Do List messages can be created or solved.

Why does updating some To Do List messages solve them?

Some To Do List messages may be caused by external causes such as custom dlls not registered or custom files not delivered. A To Do List message can also be caused by specifications, software problems, or database integrity issues. So if the external cause is solved, then updating the To Do List message solves it.

In Piping, parts get replaced by pipes when the parts are not found. Why does this happen?

In the Route application, stock parts, such as pipes and ducts, are the 'filler'. Thus, if something is missing, such as when a part is not found, then a pipe appears. The feature with the problem still exists and has a To Do List message associated with it.

When I select a To Do List message in the To Do List and do a fit, it fits all instead of the associated business object. What do I do?

Sometimes the business object has been deleted. You can refresh the list and try the fit again.

Also, sometimes the associated business object is a second class business object and may not have graphic. This should not occur; you should file a Service Request with Intergraph support in these cases.

Sometimes the geometry of the associated business object has a problem. This should not occur; you should file a Service Request in these cases.

The To Do List message description is: "Error when computing this object". How do I fix this?

Update the To Do List message to change the error description to text that is more meaningful. Turn on the error log (level 2) and update the To Do List message. The log file may contain more information.

You can also consider opening a Service Request with Intergraph. The message "Error when computing this object" is not descriptive. The error message should be more meaningful.

Do I need to remodel to solve a To Do List message?

No. However, you might try this in certain cases as a short-term solution.

Are To Do List messages and database integrity problems related?

No. However, database integrity problems can occasionally prevent solving To Do List messages. These problems can prevent semantics from processing correctly. You must monitor and reduce the number of database integrity problems whenever possible.

Are interferences linked to To Do List messages?

No interferences are generated by the interference detection server. To Do List messages may be associated to interference objects, but the To Do List messages are automatically processed.