Community
Showing results for 
Search instead for 
Do you mean 
Reply

Opportunities Pipeline View

Accepted Solution Solved
Copper Contributor
Posts: 14
Country: United_Kingdom
Accepted Solution

Opportunities Pipeline View

Using Act! Premium for Web Version: 21.1.187.0, Update 4

 

I've tried using Chrome and Edge, but whenever I try to access the Opportunities Pipeline View I get the following error message:

 

"We're sorry, there was a problem creating the Pipeline View. Please refresh this view. If you continue to see this error page, please refer to the instructions below for troubleshooting suggestions.

 

The Act! Web API was unable to authenticate the login credentials provided for this database."
 
The login credentials I am using have the Administrator security role so must have all the necessary permissions, including Web API Access.
We've been using the Act Web API for years, so I'm confident that is set up correctly.  

Accepted Solutions
Solution
Accepted by topic author soutar13
‎11-24-2020 10:41 AM
Copper Contributor
Posts: 14
Country: United_Kingdom

Re: Opportunities Pipeline View

Answering my own question, but the support team pointed me to the solution in the knowledgebase:

Configuring the API when using Custom Websites 

 

Although we are not using 'Custom Websites', I needed to update the WebAPIBaseURL key in web.config to use the full URL, e.g:

<add key="WebAPIBaseURL" value="https://<server:port>/act.web.api" />

 

I'm not sure if we were seeing the error because we're using https, or a custom port number, but it's working now.

 

View solution in original post


All Replies
Highlighted
Copper Contributor
Posts: 14
Country: United_Kingdom

Re: Opportunities Pipeline View

I forgot to add that I can log in to  <ourserver>/act.web.api using the same credentials to confirm that the API is working and the user has the right permissions.

Solution
Accepted by topic author soutar13
‎11-24-2020 10:41 AM
Copper Contributor
Posts: 14
Country: United_Kingdom

Re: Opportunities Pipeline View

Answering my own question, but the support team pointed me to the solution in the knowledgebase:

Configuring the API when using Custom Websites 

 

Although we are not using 'Custom Websites', I needed to update the WebAPIBaseURL key in web.config to use the full URL, e.g:

<add key="WebAPIBaseURL" value="https://<server:port>/act.web.api" />

 

I'm not sure if we were seeing the error because we're using https, or a custom port number, but it's working now.