Method Community

Hi, From the sounds of it, there just looks to be some confusion when setting this up.  I think while removing, deleting and recreating portal screens something was lost.  I've created new portals in both versions without issue.  None of the individual screen customizations would have had an effect. If you can replicate any of ...

Strange.  Please keep an eye on it and give us a call if it happens again. - Adam

Hi, What you'll need to do is filter the grid to only show documents for that particular customer.  Edit the grid and go to Step 3.  Add a filter to the default filter to only show documents with the entity record ID of the logged in portal user.  It should look similar to below: As long as this filter is default, when the ...

Hi Mike, Could there have been any conflicts with some of the entities or an issue with the sync?  This is definitely strange.  If it happens again, please call us so we can take a look right away. - Adam

John - Thanks for the great advice. Scott, John is dead on with his advice.  I'd recommend option 2 so you avoid altering any existing screens that are already in use.  You can see this post for instructions on a similar request.  The only difference would be to change the action from deleting to updating. Hope this helps. - ...

Hi Mike, Is it always the main account that is poplulated/not populated?  Can you replicate this, or is it completely random? - Adam

Hi 53lain, Unfortunately, I don't believe this is possible at this time.  I can put the feature request in with the team for consideration. - Adam

Mike, I would include a grid to document library table, filtered to include only documents to that activity.  You should then be able to launch it from that grid, similar to our Edit Opportunity screen. - Adam

Hi Karen, Sorry for the delay.  I actually ran into the same issue you had with the date range. There is however an easy fix for this.  Instead of using a "value from screen", I would first assign the date values to Action Results and then use those action results in the Where clause.  I will create a ticket for ...

MikeB, Glad to hear its working.  What you changed it to makes much more sense, since you're then comparing the recordID to the current row in the loop.   - Adam